New submission from Brian Curtin <cur...@acm.org>:
Debug and Release builds of py3k both throw up a Visual Studio debugger prompt
when running this test on Windows. I don't have much time at the moment to
investigate, but I find it odd that this isn't occurring on the two Windows
py3k buildbots.
Output of the release build after selecting not to debug:
C:\python-dev\py3k>PCbuild\amd64\python.exe -m test.regrtest test_capi
test_capi
test test_capi failed -- Traceback (most recent call last):
File "C:\python-dev\py3k\lib\test\test_capi.py", line 50, in
test_no_FatalError_infinite_loop
b'Fatal Python error:'
AssertionError: b"Fatal Python error: PyThreadState_Get: no current thread\r\n\r
\nThis application has requested the Runtime to terminate it in an unusual way.\
nPlease contact the application's support team for more information." != b'Fatal
Python error: PyThreadState_Get: no current thread'
1 test failed:
test_capi
----------
components: Interpreter Core, Tests
messages: 108914
nosy: brian.curtin
priority: normal
severity: normal
status: open
title: test_capi.test_no_FatalError_infinite_loop crash on Windows
type: crash
versions: Python 3.2
_______________________________________
Python tracker <rep...@bugs.python.org>
<http://bugs.python.org/issue9116>
_______________________________________
_______________________________________________
Python-bugs-list mailing list
Unsubscribe:
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
