Belcourt, Kenneth wrote:
Hi,
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.
How can one recognize such a problem?
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? ]
OK - I just uploaded the missing file. Robert Ramey
Thanks.
-- Noel
_______________________________________________ Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost