On 11/4/2010 12:31 PM, Jim Bell wrote:
Compelled as I am to audit everything, I had to compare running bjam in the lib/<x>/test directory with run.py.
I'm confident that they do produce (essentially) the same compile, link, and execute commands.
Notes, from a regression-runner's POV: * They use different directories: run.py uses {boost-root}/../results/bin.v2/..., and bjam uses {boost-root}/bin.v2/... * run.py sets up bjam with a lot of flags, like --debug-configuration [shouldn't matter for most people] -d2 [important for many, described below] -lxxx [that's lower-case L, with a time-out in seconds: potentially important]
Only important for regular regression testers as they need to make sure there are no runaway tests that impede the testing progress for other tests. Only important for authors/debuggers if they want to account for the regression tester environments, i.e. to make sure tests run in a reasonable amount of time.
preserve-test-targets=off [not sure if this matters or not] * run.py runs from the boost/status directory, I think. Might matter for some tests. Not sure about straight bjam.
Should not matter for anyone but regression testers. Since it's designed to save disk space only.
To make your own script to rebuild/rerun a particular test, run bjam with -d+2 (i.e., -d2) and direct the output to a file. Then copy the compile& link commands out of that file.
Or you could just run: cd libs/<x>/test ; bjam -a <name-of-the-test> Doing a "bjam -h" or "bjam --help" will point to other useful switches.
The -lxxx command (e.g., -l120) matters if a test could hang (e.g., <https://svn.boost.org/trac/boost/ticket/4766>).
Right :-) -- -- Grafik - Don't Assume Anything -- Redshift Software, Inc. - http://redshift-software.com -- rrivera/acm.org (msn) - grafik/redshift-software.com -- 102708583/icq - grafikrobot/aim,yahoo,skype,efnet,gmail