Bugs item #1191458, was opened at 2005-04-27 20:30
Message generated for change (Comment added) made by nnorwitz
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=105470&aid=1191458&group_id=5470
Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: Parser/Compiler
Group: AST
Status: Open
Resolution: None
Priority: 9
Submitted By: Brett Cannon (bcannon)
>Assigned to: Neal Norwitz (nnorwitz)
Summary: [AST] Failing tests
Initial Comment:
This tracker item is to be used to keep track of what
tests are currently failing on the AST branch. This is
somewhat important sinced there are so many failures it
can be hard to detect if a change fixed what it was
supposed to or actually managed to break more code.
When posting follow-ups of fixed tests, please re-list
the currently failing tests so as to make it simple to
reference the current state of things.
So, the current offenders are (from a straight
``regrtest.py`` run on my OS X box, which always has
test__locale fail so I removed it)::
test_compile test_cookielib test_dis test_doctest
test_future test_genexps test_inspect
test_itertools test_new
test_peepholer test_scope test_socket test_sort
test_subprocess
test_symtable test_syntax test_trace test_traceback
test_warnings
test_zipfile
----------------------------------------------------------------------
>Comment By: Neal Norwitz (nnorwitz)
Date: 2006-08-02 22:59
Message:
Logged In: YES
user_id=33168
Fix pending.
----------------------------------------------------------------------
Comment By: Jeremy Hylton (jhylton)
Date: 2006-04-03 08:31
Message:
Logged In: YES
user_id=31392
Just wanted to note that I have fixes for the failing tests
on my laptop. Need to sync with the current trunk before I
can check in.
----------------------------------------------------------------------
Comment By: Brett Cannon (bcannon)
Date: 2005-10-25 15:03
Message:
Logged In: YES
user_id=357491
Yep, all tests pass, so that just leaves the test_trace
tests that are currently commented out.
----------------------------------------------------------------------
Comment By: Neil Schemenauer (nascheme)
Date: 2005-10-23 21:51
Message:
Logged In: YES
user_id=35752
I believe the only remaining broken tests are the ones
commented out in test_trace.
----------------------------------------------------------------------
Comment By: Jeremy Hylton (jhylton)
Date: 2005-10-07 11:46
Message:
Logged In: YES
user_id=31392
test_dis update:
Fixed one of two failing tests. test_dis() was easy.
test_bug_708901() is harder. The current AST only stores
line numbers for statements. The test case is checking that
the lnotab can assign a single statement multiple line
numbers; in this case, the statement spans multiple lines
and the disassembled code should reflect that. The fix is
probably to add line numbers to expressions, which requires
changing the AST definition and updating ast.c to assign
line numbers.
----------------------------------------------------------------------
Comment By: Jeremy Hylton (jhylton)
Date: 2005-10-07 11:01
Message:
Logged In: YES
user_id=31392
Here's a quick status report on Linux + GCC 3.2.2 from today:
12 tests failed:
test_dis test_doctest test_future test_genexps test_inspect
test_new test_peepholer test_pwd test_scope test_subprocess
test_symtable test_trace
7 skips unexpected on linux2:
test_hotshot test_bsddb test_email test_parser
test_transformer
test_email_codecs test_compiler
I'm going to trace into the details of why each of these
tests is failing.
----------------------------------------------------------------------
Comment By: Brett Cannon (bcannon)
Date: 2005-07-10 21:15
Message:
Logged In: YES
user_id=357491
Scratch the "all open bugs" comment; didn't get to bug #1195576.
----------------------------------------------------------------------
Comment By: Brett Cannon (bcannon)
Date: 2005-07-10 21:13
Message:
Logged In: YES
user_id=357491
After applying all patches associated with all open bugs,
the failing tests from ``./python.exe Lib/test/regrtest.py``
are:
14 tests failed:
test_cookielib test_dis test_future test_genexps
test_inspect
test_new test_peepholer test_scope test_subprocess
test_symtable
test_syntax test_trace test_traceback test_warnings
----------------------------------------------------------------------
Comment By: Nick Coghlan (ncoghlan)
Date: 2005-05-28 04:40
Message:
Logged In: YES
user_id=1038590
Fixing #1186353 (lambda argument unpacking) fixes test_sort and
test_itertools:
17 tests failed:
test_compile test_cookielib test_dis test_doctest test_future
test_genexps test_inspect test_new test_ossaudiodev
test_peepholer
test_scope test_subprocess test_symtable test_syntax test_trace
test_traceback test_warnings
----------------------------------------------------------------------
Comment By: Nick Coghlan (ncoghlan)
Date: 2005-05-28 01:33
Message:
Logged In: YES
user_id=1038590
Bumped bug priority to 9 so it stays on top of the SF tracker. Also, we
can't merge the AST branch until this bug is closed, so it is fairly
important to close out these issues :)
Running "./python Lib/test/regrtest.py -uall"
Suse Linux 9.1:
20 tests failed:
test_compile test_cookielib test_dis test_doctest test_future
test_genexps test_inspect test_itertools test_new test_ossaudiodev
test_peepholer test_scope test_sort test_subprocess
test_symtable
test_syntax test_trace test_traceback test_warnings test_zipfile
WIth the patch for 1186195 (genexp scoping) applied I get:
19 tests failed:
test_compile test_cookielib test_dis test_doctest test_future
test_genexps test_inspect test_itertools test_new test_ossaudiodev
test_peepholer test_scope test_sort test_subprocess
test_symtable
test_syntax test_trace test_traceback test_warnings
The remaining test_genexps failures are due to assignment
statements not checking for genexps as illegal targets. Running
test_zipfile in verbose mode indicated genexp problems, so it makes
sense that fixing the scoping eliminated those failures.
I'm going to look at lambdas next, since they seem to be the culprits
with respect to a few different test failures.
----------------------------------------------------------------------
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=105470&aid=1191458&group_id=5470
_______________________________________________
Python-bugs-list mailing list
Unsubscribe:
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
