Subject: Re: [boost] Trunk tests broken
From: Belcourt, Kenneth (kbelco_at_[hidden])
Date: 2010-06-02 15:06:24
On Jun 2, 2010, at 12:36 PM, Beman Dawes wrote:
> On Wed, Jun 2, 2010 at 1:41 PM, Belcourt, Kenneth
> <kbelco_at_[hidden]> wrote:
>> Could I suggest that when the trunk tests are completely broken, as
>> they are
>> now, and the report generation is cycling normally (every 1 to 2
>> hours) as
>> it is now, that the likely source of breakage is a recent commit to
>> trunk repository. To reproduce the trunk failure, simply checkout
>> out a
>> current version of the trunk, cd to the status directory, and run
>> bjam. If
>> you do this right now, you'll find this error message.
>> error: Unable to find file or target named
>> error: 'test_diamond_complex.cpp'
>> error: referred from project at
>> error: '../libs/serialization/test'
>> This is what's currently killing trunk testing.
> bjam shouldn't stop entirely because a file isn't found. At worst,
> that library's tests should fail.
And all libraries that depend on the broken library will also likely
> Can Boost.Build or bjam be modified to be more tolerant of errors
> during regression testing?
Fair question. I suspect so but I've never looked into what it would
Boost list run by bdawes at acm.org, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk