Case Van Horsen <cas...@gmail.com> added the comment:
On Win64, I get two unexpected failures:
I terminated test_capi after a Windows exception box popped up.
[ 37/349] test_capi
test test_capi failed -- Traceback (most recent call last):
File "C:\svn\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 term
inate it in an unusual way.\nPlease contact the application's support team for
more information." != b'Fatal Python error: PyThreadS
tate_Get: no current thread'
[ 67/349] test_concurrent_futures
test test_concurrent_futures failed -- Traceback (most recent call last):
File "C:\svn\py3k\lib\test\test_concurrent_futures.py", line 442, in
test_timeout
future1]), finished)
AssertionError: Items in the second set but not the first:
<Future at 0x5510fd0 state=finished raised AssertionError>
The dictviews test passes successfully.
----------
status: pending -> open
_______________________________________
Python tracker <rep...@bugs.python.org>
<http://bugs.python.org/issue9778>
_______________________________________
_______________________________________________
Python-bugs-list mailing list
Unsubscribe:
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
