[ python-Bugs-1054615 ] New failure in debug build
SourceForge.net
noreply at sourceforge.net
Tue Oct 26 17:14:59 CEST 2004
Bugs item #1054615, was opened at 2004-10-26 10:17
Message generated for change (Comment added) made by tim_one
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=105470&aid=1054615&group_id=5470
Category: Python Interpreter Core
Group: Python 2.4
Status: Open
Resolution: None
Priority: 9
Submitted By: Tim Peters (tim_one)
Assigned to: Nobody/Anonymous (nobody)
Summary: New failure in debug build
Initial Comment:
This is current CVS Python. Sorry, no idea what caused
this; it started within the last day (or two at the most):
C:\Code\python\PCbuild>python_d ..\lib\test\test_traceb
ack.py
test_bug737473 (__main__.TracebackCases) ... ERROR
test_caret (__main__.TracebackCases) ... ok
test_nocaret (__main__.TracebackCases) ... ok
==========================================
============================
ERROR: test_bug737473 (__main__.TracebackCases)
------------------------------------------------------
----------------
Traceback (most recent call last):
File "..\lib\test\test_traceback.py", line 62, in
test_bug737473
import test_bug737473
SystemError: NULL result without error in PyObject_Call
------------------------------------------------------
----------------
Ran 3 tests in 0.078s
FAILED (errors=1)
Traceback (most recent call last):
File "..\lib\test\test_traceback.py", line 90, in ?
test_main()
File "..\lib\test\test_traceback.py", line 86, in test_main
run_unittest(TracebackCases)
File "C:\Code\python\lib\test\test_support.py", line
290, in run_unittest
run_suite(suite, testclass)
File "C:\Code\python\lib\test\test_support.py", line
275, in run_suite
raise TestFailed(err)
test.test_support.TestFailed: Traceback (most recent
call last):
File "..\lib\test\test_traceback.py", line 62, in
test_bug737473
import test_bug737473
SystemError: NULL result without error in PyObject_Call
[12133 refs]
C:\Code\python\PCbuild>
----------------------------------------------------------------------
>Comment By: Tim Peters (tim_one)
Date: 2004-10-26 11:14
Message:
Logged In: YES
user_id=31435
Sorry to hear that -- I can't make time to dig. I blew away
everything and recompiled from scratch, and the problem
didn't go away.
----------------------------------------------------------------------
Comment By: Michael Hudson (mwh)
Date: 2004-10-26 10:51
Message:
Logged In: YES
user_id=6656
"Works for me" (linux). Something Windows specific?
The obviously suspicious recent change is patch #737473
which perky checked in yesterday -- but that was a pure
Python change, so there must be something more to it than that.
----------------------------------------------------------------------
Comment By: Tim Peters (tim_one)
Date: 2004-10-26 10:19
Message:
Logged In: YES
user_id=31435
Noting that I also see this failure in a release build.
----------------------------------------------------------------------
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=105470&aid=1054615&group_id=5470
More information about the Python-bugs-list
mailing list