test_read_write_mutex trouble under Tru64 Unix
Last night I started Aleksey's regression.py script under Tru64 Unix. It used to finish after 6 hours, but now the test_read_write_mutex process has consumed 16 CPU hours already without finishing. I am going to kill it. I hope the failure shows up at the meta-comm site. Let me know if more information is required. Ralf _______________________________ Do you Yahoo!? Win 1 of 4,000 free domain names from Yahoo! Enter now. http://promotions.yahoo.com/goldrush
Ralf W. Grosse-Kunstleve wrote:
Last night I started Aleksey's regression.py script under Tru64 Unix. It used to finish after 6 hours, but now the test_read_write_mutex process has consumed 16 CPU hours already without finishing. I am going to kill it. I hope the failure shows up at the meta-comm site. Let me know if more information is required.
I had the same problem on my linux platform yesterday. I had to kill that one (and the next on I think) in order to complete the regerssion runs. Markus
--- "Ralf W. Grosse-Kunstleve" <rwgk@yahoo.com> wrote:
Last night I started Aleksey's regression.py script under Tru64 Unix. It used to finish after 6 hours, but now the test_read_write_mutex process has consumed 16 CPU hours already without finishing. I am going to kill it. I hope the failure shows up at the meta-comm site. Let me know if more information is required.
I had to use the kill command a few more times. I don't think the results made it to the meta-comm server. The output of regression.py is available here: http://cci.lbl.gov/~rwgk/tmp/tru64cxx65_boost_regression/ The file name is run_2004_08_18_0207.log. The file run_regression.csh was used to start the tests. Ralf _______________________________ Do you Yahoo!? Win 1 of 4,000 free domain names from Yahoo! Enter now. http://promotions.yahoo.com/goldrush
Ralf W. Grosse-Kunstleve wrote:
Last night I started Aleksey's regression.py script under Tru64 Unix. It used to finish after 6 hours, but now the test_read_write_mutex process has consumed 16 CPU hours already without finishing. I am going to kill it. I hope the failure shows up at the meta-comm site. Let me know if more information is required. Ralf
There are some problems with the read_write_mutex, though I wasn't aware of the problem you mention. I'm trying to fix the problems, but am catching up from being on vacation last week and am also having to deal with the Boost.Threads regression results seemingly getting worse each day due to changes in other libraries. I'll commit fixes to read_write_mutex as soon as I'm able. Sorry for the problems, Mike
participants (3)
-
Markus Schöpflin -
Michael Glassford -
Ralf W. Grosse-Kunstleve