Issue 10098: intermittent failure in test_os (original) (raw)

Issue10098

➜

This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

This issue has been migrated to GitHub: https://github.com/python/cpython/issues/54307

classification

process

Created on 2010-10-14 08:34 by pitrou, last changed 2022-04-11 14:57 by admin. This issue is now closed.

Messages (5)
msg118634 - (view)	Author: Antoine Pitrou (pitrou) *	Date: 2010-10-14 08:34
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_with_event(signal.CTRL_BREAK_EVENT, "CTRL_BREAK_EVENT") File "D:\cygwin\home\db3l\buildarea\3.x.bolen-windows7\build\lib\test\test_os.py", line 1058, in _kill_with_event self.fail("subprocess did not stop on {}".format(name)) AssertionError: subprocess did not stop on CTRL_BREAK_EVENT http://www.python.org/dev/buildbot/3.x.stable/builders/x86%20Windows7%203.x/builds/1755/steps/test/logs/stdio
msg118676 - (view)	Author: Brian Curtin (brian.curtin) *	Date: 2010-10-14 15:58
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.
msg118747 - (view)	Author: Amaury Forgeot d'Arc (amaury.forgeotdarc) *	Date: 2010-10-15 07:22
_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.
msg118778 - (view)	Author: Brian Curtin (brian.curtin) *	Date: 2010-10-15 14:23
That works for me locally. Checked in that 0 to 1 change in r85525 - waiting to see if it works on the slower buildbots.
msg118873 - (view)	Author: Hirokazu Yamamoto (ocean-city) *	Date: 2010-10-16 15:19
Sorry about this. And thank you for fix.