On Friday 04 October 2013 01:56:10 you wrote:
On Thursday 03 October 2013 16:37:45 Tom Kent wrote:
So are you sure the flag is just --timeout=10? I have that in my script, but it doesn't seem to be picking it up...aka when the command is put at the bottom of the html page for the test runner, it shows the command correctly, but without that part of it. Is it possible that it is getting thrown out by run.py somehow?
http://www.boost.org/development/tests/trunk/teeks99-03a-win2008-64on64.ht ml
The actual command I'm running:
python run.py --runner=teeks99-03a-win2008-64on64 --force-update --toolsets=msvc-8.0 --bjam-options="-j2 address-model=64" --timeout=10 --comment=..\info.html --timeout=10 2>&1 | ..\wtee output.log
The one that shows up in the above link:
run.py --runner=teeks99-03a-win2008-64on64 --force-update --toolsets=msvc-8.0 \ "--bjam-options=\"-j4 address-model=64\"" --comment=..\\info.html
Any ideas what is going on here?
I don't know, I've never set up a testing machine for Boost before. The parameter does seem to be present for some other testers, for instance:
http://www.boost.org/development/tests/trunk/VC8%20jc-bell-com.html
Tom, is it possible that multiple builds are run simultaneously on the same machine, and because each build tries to utilize all CPUs the whole system becomes overutilized? Just an idea of a possible cause of such long builds. Also, I've committed a change yesterday, which may save a few seconds of building (at least it did save as much on my setup).