These particular ones are due to the fact that I've never been able to force the order of tests with bjam. Those tests attempt to load archives which haven't been created yet. If one doesn'st clean out the $TMPDIR, these errors don't occur the next time. Using the markup to indicate - fails sometimes resulted in a misleading marking of the passing tests (If I remember correctly) so I just had to leave it. That is, the "fail" are really artifacts of the bjam implementation. Robert Ramey Douglas Gregor wrote:
On Jul 28, 2005, at 3:52 AM, Martin Wille wrote:
I'm felt somewhat irritated by the discrepancies between OSL's results for Boost.Serialization and mine.
However, I now see that exactly 10 tests are affected. I also found out that Boost.Serialization tests leave a multiple of 10 files in /tmp on my HD.
Could it be that the tests are unable to create the files on the OSL2 machine? This would explain the "std::exception: stream error" output from those tests.
I haven't been able to track these down, but every time I've run the tests outside of the regression.py, everything works fine. I've just cleared out /tmp and started running the tests again...
Doug
_______________________________________________ Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost