[issue10098] intermittent failure in test_os

[Hirokazu Yamamoto]

Hirokazu Yamamoto  added the comment:

Sorry about this. And thank you for fix.

--

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue10098] intermittent failure in test_os

[Brian Curtin]

Changes by Brian Curtin :


--
resolution:  -> fixed
stage: commit review -> committed/rejected
status: open -> closed

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue10098] intermittent failure in test_os

[Brian Curtin]

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 

___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue10098] intermittent failure in test_os

[Amaury Forgeot d'Arc]

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: +amaury.forgeotdarc

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue10098] intermittent failure in test_os

[Brian Curtin]

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 

___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue10098] intermittent failure in test_os

[Antoine Pitrou]

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_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

--
components: Tests, Windows
messages: 118634
nosy: brian.curtin, db3l, pitrou, tim.golden
priority: normal
severity: normal
status: open
title: intermittent failure in test_os
type: behavior
versions: Python 3.2

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com