Boost logo

Boost :

From: Michael Glassford (glassfordm_at_[hidden])
Date: 2004-07-21 08:14:50


The latest regression results for test_read_write_mutex at
http://boost.sourceforge.net/regression-logs/cs-Linux/developer/thread.html
report a number of different errors on different compilers, the most
common being

<quote>
Assertion failed: valid_read_lock(m_state), file
C:\Users\administrator\main\boost\libs\thread\build\..\src\read_write_mutex.cpp,
line 218
</quote>

This indicates to me that these regression tests were run without the
changes I checked in yesterday afternoon. Is this just because it takes
so long to run regression tests that I have to wait for the next run to
find out how my changes worked, or is there another reason?

Also, the only reason I can tell that the regression tests were run
without recent changes is because the changes were significant enough
that the assertion in question is no longer anywhere near line 218. Is
there any possibility at some point in the future of adding information
to the regression log indicating what version of each source file was
used to run the tests? I realize that this information isn't directly
available to the regression testing tools, but perhaps the build process
could be modified to record the cvs version information for each source
file it uses (not sure how it would get it) whenever it builds anything,
and the information could be incorporated into the regression reports?

Mike


Boost list run by bdawes at acm.org, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk