Boost Testing :
From: John Maddock (john_at_[hidden])
Date: 2005-04-18 05:21:26
>> unicode_iterator_test is failing at runtime with gcc-2.95.3, but passes
>> when run locally on my machine (I'm fairly sure that the error shown may
>> have been a real issue at some point, but shouldn't be now IMO).
> The test binary for unicode_iterator_test/gcc-2.95.3 and the associated
> XML file on my Machine date back to 2004-02-15. Why doesn't it get rebuilt
> when there was a code change to fix the errors? Could this be a result of
> a failure in building some depend code which doesn't cause the XML file to
> get deleted (that's the only idea I have)?
If I remember correctly this one was down to a temporary problem in
Boost.Test: the changes to the Boost.Test headers (the macros changed)
should have triggered a rebuild. I have seen before though that changes to
library dependencies don't always trigger rebuilds.
> I'll delete the build- and the test-tree after the current run.