Boost Testing :
From: K. Noel Belcourt (kbelco_at_[hidden])
Date: 2007-09-15 13:26:52
On Sep 14, 2007, at 9:37 AM, K. Noel Belcourt wrote:
> On Sep 14, 2007, at 9:30 AM, Rene Rivera wrote:
>> Doug Gregor wrote:
>>> The upgradeable_mutex_test test in the interprocess library is
>>> deadlocking on sun-5.8 (Sparc).
>>> This kind of problem is breaking our regression testing too often.
>>> It's not Ion's fault: the regression testing needs to be robust
>>> against this kind of failure. On Windows, we have the built-monitor
>>> option to kill stuck processes. On Unix, we could just set the
>>> and be done with it... but how to integrate this into bjam/BBv2?
>> First, don't use build monitor :-) Use the bjam -l option. And
>> we just need to someone familiar enough with sub-process
>> management on
>> Unix (and it's variants) to implement the -l option
> This sounds like fun. I'll take a look.
I've got this in and working. What's a reasonable value for -l when
running the Boost regression tests, 300 seconds, 30 seconds? I
realize that different hardware will require different values but
what do you think is reasonable upper limit for Boost tests in general?