I`ve got some advices, may be they will be useful. 2011/5/10 Christopher Jefferson <chris@bubblescope.net>:
1) Running the boost regression tests takes unacceptably long. I would like to run tests for clang with and without libc++, with and without c++0x mode. Running those 4 sets of tests takes a huge amount of time. Various tests (and I keep meaning to try to find which ones) take huge amounts of memory, meaning it isn't reasonable to run even a single-threaded boost regression test in the background on a 4GB machine. Running tests in parallel doesn't seem to speed them up particularly, while bringing the machine even more onto it's knees.
Agree. But usually, I run not all tests for all the libraries, but just for the required library. If you are using run.py, than take a look at options --force-update and --timeout=TIMEOUT at http://www.boost.org/development/running_regression_tests.html, they may help in reducing download times and getting the names of the heavy tests.
2) The boost regression testpage ( http://www.boost.org/development/tests/trunk/developer/summary.html ) is fairly useless, as it doesn't say when a particular test failed. This means I just have to try to memorise the current state of all the compilers I am interested in, and look for new fails by eyeball. Much more useful would be changing the 'fail' to the most recent svn version at which a new fail occurred?
Agree, but it is possible to look at the regression test time and get svn history with timestamps, to see, which commit break the tests. It`s not really comfortable, but works.
3) I always find trac hard to use. I usually want to do 2 things: a) Find all open bugs attached to package X
You can create your own filter/report: just go to the track -> View tickets -> Custom Query (it is near the "Server load")
b) List all bugs which I filed, or have have submitted a message to.
https://svn.boost.org/trac/boost/report/7 (don`t forget to login) Best regards, Antony Polukhin