|
Size: 1653
Comment: fewer failing tests
|
Size: 1846
Comment: more passing tests
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 7: | Line 7: |
| * test_doctest - unicode problem | |
| Line 9: | Line 10: |
| * test_inspect - getsource (no surprise with this type of issue) * test_operator - various things raise AttributeError instead of TypeError * test_runpy - no PySystemState.startswith; no imp.getmagic |
* test_inspect * test_multibytecodec * test_multibytecodec_support |
| Line 14: | Line 15: |
| * test_tempfile - 1 failure, test_usable_template | |
| Line 15: | Line 17: |
| * test_univnewlines - test_doctest failures don't restore sys.stdin -- causes to skip (it normally passes) * test_with - we're generating bad bytecode with nested yields, e.g. with manager(): yield 1 (testWithYields) |
|
| Line 21: | Line 25: |
| * test_tuple - sometimes with OutOfMemoryError during regrtest | * test_socket - historically this is the case on SO_RCVBUF, SO_SNDBUF * test_tuple - sometimes OutOfMemoryErrors during regrtest (when creating a set from a large list of small tuples). maybe not the tests fault, but the fact that the regrtest progressively uses more and more memory as it goes: http://pylonshq.com/pasties/917 |
| Line 26: | Line 31: |
| * test_builtin - compile/exec/eval problems | |
| Line 29: | Line 35: |
| * test_distuils - SyntaxError when attempting to py_compile to $py.class (probably parser newline problems) * test_doctest - exec doesn't work * test_future - probably bad line numbers |
* test_future - bad line numbers |
| Line 33: | Line 37: |
| * test_java_integration - ReservedNamesTest (in/exec), also there's class * test_jy_compile - not rejecting syntax, is there an issue with exec code in a_dict? * test_traceback - not rejecting bad indentation |
Development =========== * test__rawffi (for ctypes, ported from PyPy) |
To Fix
- test_coercion - __cmp__ doesn't utilize __coerce__?
- test_doctest - unicode problem
- test_generators - not rejecting incorrect syntax wrt yield; but others need to be resolved outside of parser (maybe eval order?); fibgen is causing parse issues; tracebacks have extra blank lines apparently
- test_genexps - need to test iterability of an object like int; similar syntax issues as test_generator
- test_inspect
- test_multibytecodec
- test_multibytecodec_support
- test_site - del sys.setdefaultencoding does nothing
- test_struct - needs new 2.5 struct.Struct type and pack_into/unpack_from
- test_tempfile - 1 failure, test_usable_template
- test_unicode - lack of idna encoding (which needs unicodedata)
- test_univnewlines - test_doctest failures don't restore sys.stdin -- causes to skip (it normally passes)
- test_with - we're generating bad bytecode with nested yields, e.g. with manager(): yield 1 (testWithYields)
- test_zipfile - possibly struct issues?
Flaky/arch?
- test_scope - sometimes fails due to GC
- test_socket - historically this is the case on SO_RCVBUF, SO_SNDBUF
- test_tuple - sometimes OutOfMemoryErrors during regrtest (when creating a set from a large list of small tuples). maybe not the tests fault, but the fact that the regrtest progressively uses more and more memory as it goes: http://pylonshq.com/pasties/917
Parser
- test_builtin - compile/exec/eval problems
- test_compile - over acceptance of incorrect syntax; need to raise problems with unicode being declared to have an encoding!
- test_contextlib - likely parser eval order
- test_decorators - eval order
- test_future - bad line numbers
- test_genexp, test_generator - parser probs
Development
- test__rawffi (for ctypes, ported from PyPy)