[issue10098] intermittent failure in test_os

Hirokazu Yamamoto added the comment: Sorry about this. And thank you for fix. -- ___ Python tracker ___ ___ Python-bugs-list mailing

[issue10098] intermittent failure in test_os

Changes by Brian Curtin : -- resolution: -> fixed stage: commit review -> committed/rejected status: open -> closed ___ Python tracker ___ __

[issue10098] intermittent failure in test_os

Brian Curtin added the comment: That works for me locally. Checked in that 0 to 1 change in r85525 - waiting to see if it works on the slower buildbots. -- stage: -> commit review ___ Python tracker

[issue10098] intermittent failure in test_os

Amaury Forgeot d'Arc added the comment: _kill_with_event() does not wait for the subprocess to be ready. It seems to me that the following test is wrong: if m[0] == 0: It should be "if m[0] == 1", since we want to check that the subprocess updated the shared memory. -- nosy: +amaur

[issue10098] intermittent failure in test_os

Brian Curtin added the comment: I've noticed this a few times since r85315. It raises a dialog box saying "The application was unable to start correctly" for some reason. -- nosy: +ocean-city ___ Python tracker _

[issue10098] intermittent failure in test_os

New submission from Antoine Pitrou : The Windows 7 buildbot sometimes shows a failure in test_os: test test_os failed -- Traceback (most recent call last): File "D:\cygwin\home\db3l\buildarea\3.x.bolen-windows7\build\lib\test\test_os.py", line 1080, in test_CTRL_BREAK_EVENT self._kill_wi