Whether any of these are "bugs" or not is up to you, but they are nuissances for my test runs: * module._stackless.test.test_choicepoint http://scottdial.com/pypytest/31094/failed/module._stackless.test.test_choic... This test gets stalled while running a subprocess (testing_1.exe) and I must manually kill this process for the testing to continue. I haven't been able to identify the problem. * translator.c.test.test_stackless.TestStackless().test_stack_too_big http://scottdial.com/pypytest/31094/failed/translator.c.test.test_stackless.... This test causes the boehm gc library to throw and catch an exception "Too many heap sections". I suspect this means that the test has indeed failed. However, this assertion from the gc library is modal and blocking, so it stalls the test run until human intervention clicks "ok". I haven't looked deeply into this one. Otherwise, none of the failures require human involvement to get things going again, but there are plenty of other tests which are erroneous failures. -- Scott Dial scott@scottdial.com scodial@indiana.edu
Hi Scott, On Sun, Aug 13, 2006 at 06:58:36AM -0400, Scott Dial wrote:
Whether any of these are "bugs" or not is up to you, but they are nuissances for my test runs:
We'll try to look into them, but for now, feel free to skip them. (You can probably just drop a py.test.skip("XXX") in the tests in your automated runner's working copy.) A bientot, Armin
participants (2)
-
Armin Rigo
-
Scott Dial