On Wed, Jun 2, 2010 at 1:41 PM, Belcourt, Kenneth <kbelco@sandia.gov> wrote:
Hi,
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 the 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. Can Boost.Build or bjam be modified to be more tolerant of errors during regression testing? --Beman