|
|
Boost Testing : |
From: Rene Rivera (grafikrobot_at_[hidden])
Date: 2007-09-27 10:13:45
Jason Sankey wrote:
> Rene Rivera wrote:
>> We've noticed that and similar hangs recently. Which is why Noel spent
>> time last week implementing the bjam time limit feature on Unix we've
>> had on Windows for some time. Just add a "-l300", or more than 300
>> seconds if you like, to the bjam invocation that runs the tests.
>
> I see, and thanks for the tip! Will using this option allow other tests
> to be run and their results captured, or will any tests that normally
> come after interprocess be skipped? I can also set up a build timeout
> in Pulse that will stop things hanging indefinitely.
Since it stops only the individual build action this will let the rest
of the tests to continue, and hence captured.
> There is still the question of how to get the issue resolved? This
> failure seems fairly reliable: no occurrences over a couple of weeks
> (several builds/day) and now I have three hung builds in a row.
Only way to resolve it is for the library author to fix the bug :-)
Which since the test fails he'll get email about it every day.
-- -- Grafik - Don't Assume Anything -- Redshift Software, Inc. - http://redshift-software.com -- rrivera/acm.org - grafik/redshift-software.com -- 102708583/icq - grafikrobot/aim - grafikrobot/yahoo