THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY. A new Flyspray task has been opened. Details are below.
User who did this: - Steve Reinhardt (stever) Attached to Project - M5 Bugs Summary - Regressions no longer retry on user kill Task Type - Bug Category - Testing Status - New Assigned To - Operating System - All Severity - Medium Priority - Normal Reported Version - 2.0beta5 Due in Version - Due Date - Undecided Details - There's some code I added to tests/SConscript that intentionally avoids creating the 'status' output file if m5 terminates with one of a certain set of signals such as SIGINT. (Grep for retry_signals in that file to see where.) Without this code, premature termination of m5 counts as a test failure (as is often appropriate, e.g., if you hit an assertion failure or SIGSEGV). The intended effect here is that if you ^C a regression test for some reason then restart it, it will re-run the test automatically, rather than reporting a failed test and requiring you to go delete the output files to force scons to re-run it. This used to work (I know it did when I added this code in March 2009, see http://repo.m5sim.org/m5/rev/e0344c15e73b). It doesn't anymore; I just ^C'd a regression and got the old behavior. I suspect the interrupt return code is getting lost in the transition from C++ to Python, but a quick skim doesn't turn up any changes since then that would look suspicious, and I don't have time to dig into this right now. Anything come to mind, Nate? More information can be found at the following URL: http://www.m5sim.org/flyspray/task/330 You are receiving this message because you have requested it from the Flyspray bugtracking system. You can be removed from future notifications by visiting the URL shown above. _______________________________________________ m5-dev mailing list m5-dev@m5sim.org http://m5sim.org/mailman/listinfo/m5-dev
