run.py building with multiple toolsets fails

[Antony Polukhin]

Foolowing command failed:

python run.py --runner=apolukhin-ubuntu --bjam-toolset=gcc --pjl-toolset=gcc --bjam-options=-j2 --toolsets=gcc-4.3,gcc-4.4,gcc-4.5,clang,intel --force-update

Build logs and user-config.jam are attached. Platform is Linux x86_64 (ubuntu)
If I`m doing somethig wrong, please tell about it and update the documentation

[Antony Polukhin]

Output to console

[Antony Polukhin]

Recursive dump of test build folder and subdirectories

[Steven Watanabe]

What's in results/bjam.log? That's where the error will show up.

[Antony Polukhin]

Replying to steven_watanabe:

What's in results/bjam.log? That's where the error will show up.

Added bjam.log
It gave me no clue about what I am doing wrong

[Steven Watanabe]

That's interesting...

Can you try running the bjam command directly from the command line? Is it running out of memory?

[Antony Polukhin]

Is it running out of memory?

When I run run.py with a single toolset, it works perfectly.
I`ve run the following command

"/home/antoshkka/boost_maintain/full_test/tools_bjam/bin.linuxx86_64/bjam" "-sBOOST_BUILD_PATH=/home/antoshkka/boost_maintain/full_test:/home/antoshkka/boost_maintain/full_test/tools_bb" "-sBOOST_ROOT=/home/antoshkka/boost_maintain/full_test/boost" "--boost=/home/antoshkka/boost_maintain/full_test/boost" "--boost-build=/home/antoshkka/boost_maintain/full_test/tools_bb" "--debug-configuration"  -l300 gcc-4.3 gcc-4.4 gcc-4.5 clang intel -d2 preserve-test-targets=off --dump-tests -j2 "--build-dir=/home/antoshkka/boost_maintain/full_test/results" >"/home/antoshkka/boost_maintain/full_test/log.log" 2>&1

and the last rows of log file are

notice: will use 'icpc' for intel-linux, condition <toolset>intel-linux
notice: using intel libraries :: <toolset>intel-linux :: /opt/intel/composerxe-2011.3.174/bin/lib /opt/intel/composerxe-2011.3.174/lib/intel64
/home/antoshkka/boost_maintain/full_test/tools_bb/build/feature.jam:320: in validate-feature from module feature
error: unknown feature "<preserve-test-targets>"
/home/antoshkka/boost_maintain/full_test/tools_bb/build/feature.jam:354: in expand-subfeatures-aux from module feature
/home/antoshkka/boost_maintain/full_test/tools_bb/build/feature.jam:419: in feature.expand-subfeatures from module feature
/home/antoshkka/boost_maintain/full_test/tools_bb/build/build-request.jam:20: in apply-to-property-set from module build-request
/home/antoshkka/boost_maintain/full_test/tools_bb/kernel/modules.jam:103: in modules.call-in from module build-request
/home/antoshkka/boost_maintain/full_test/tools_bb/util/sequence.jam:48: in sequence.transform from module sequence
/home/antoshkka/boost_maintain/full_test/tools_bb/build/build-request.jam:32: in build-request.expand-no-defaults from module build-request
/home/antoshkka/boost_maintain/full_test/tools_bb/build-system.jam:624: in load from module build-system
/home/antoshkka/boost_maintain/full_test/tools_bb/kernel/modules.jam:283: in import from module modules
/home/antoshkka/boost_maintain/full_test/tools_bb/kernel/bootstrap.jam:142: in boost-build from module
/home/antoshkka/boost_maintain/full_test/boost-build.jam:17: in module scope from module

Did you mean that command?

[Antony Polukhin]

Replying to steven_watanabe:

Is it running out of memory?

I`ve done some more tests and yes, it is running out of memory.
May be instead of building with all tool-sets simultaneously, bjam shall use one toolset at a time? That would reduce memory usage, and build parallelism can be still controlled via --bjam-options=-jN