Subject: Re: [boost] [test] Trunk broken: What happened to test_exec_monitor?
From: Belcourt, Kenneth (kbelco_at_[hidden])
Date: 2011-10-04 19:25:53
On Oct 4, 2011, at 5:10 PM, Gennadiy Rozental wrote:
> Belcourt, Kenneth <kbelco <at> sandia.gov> writes:
>> A suggestion, once you've reverted all your recent changes,
>> wait for tests to cycle and concentrate on
>> fixing ALL the broken Boost.Test testers before you apply
>> any of your new changes. I like to first see a
>> green Boost.Test for all testers before we start down this
>> path again.
> What testers you mean? Unit tests? Do you suggest they were broken before I
> checked in my changes?
Sorry if I wasn't clear. Boost.Test in trunk was not green for several Sandia testers on Darwin and perhaps other platforms but I can't recall them all at the moment. But I've been most concerned about Boost.Test on Darwin as a number of developers have asked me to debug Darwin Intel problems with their libraries that, from what I can tell, originate in Boost.Test. I've replied to those developers that I think we need Boost.Test on Darwin Intel to work correctly (passing all tests) before I can invest much time trying to debug their code. I suspect many of the other library problems will vanish once your library is passing all of its tests.
Boost list run by bdawes at acm.org, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk