On 2014-01-27 9:54 AM, Marshall Clow wrote:

On Jan 25, 2014, at 5:49 PM, Marshall Clow <mclow.lists@gmail.com> wrote:

...
Here’s the invocation:

cd /Volumes/TwoTB/boost/regression/develop
python run.py --runner=marshall-mac --tag=develop \
--toolsets=darwin,clang,clang-11,clang-tot,clang-tot11,clang-asan,clang-asan11 \
--bjam-toolset=darwin --pjl-toolset=darwin --bjam-options="-j 12”

I came in to work this morning, and my machine was still doing this.

More precisely, “process_jam_log” was running, taking 100% of one core, and apparently has been doing so for many, many hours.

I’d put up “bjam.log” for people to look at, but it is 11.6 GB long.

Suggestions?

Give it a little more time to finish? (Just kidding!)

Maybe break the toolsets out one at a time.

process_jam_log is post-bjam (right?) so its messages would be from a capture of run.py's stdout/stderr. Are you capturing that? Anything interesting there?