[boost] Trunk tests broken

Subject: [boost] Trunk tests broken
From: Belcourt, Kenneth (kbelco_at_[hidden])
Date: 2010-06-02 13:41:38

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.

Since it's quite easy to reproduce the trunk failure, I think it would  
help Boost if developers would, when they recognize a problem, either  
revert the offending commit or ping the library author(s) to let them  
know about the breakage.  Unfortunately I am unable to keep on top of  
when trunk testing is broken (i.e. it could be several days before I  
notice it) so if other developers could help diagnose breakage and  
report it, that would be very helpful.

[ Robert, can you please address this issue? ]

Thanks.

-- Noel