Differences between revisions 2 and 198 (spanning 196 versions)
Revision 2 as of 2007-07-10 14:04:43
Size: 1942
Editor: 213
Comment:
Revision 198 as of 2007-08-17 16:50:18
Size: 2740
Editor: 65
Comment:
Deletions are marked like this. Additions are marked like this.
Line 1: Line 1:
= List of tests that are failing in the py3k-struni branch = (Back to ["Python3000"].)
Line 3: Line 3:
(Back to ["Python3000"].) = List of tests that are failing in the py3k branch =
Line 7: Line 7:
  * if you start working on a test, to avoid duplicate work, add your name+email+date to the bulleted item for the test below, with the text "FIXING" or "INVESTIGATING"   * if you start working on a test, to avoid duplicate work, add your name+email+date to the bulleted item for the test below, with the text "MINE"
Line 9: Line 9:
  * if you fix a test, and you check in the fix, add a note "FIXED" (occasionally we'll clean these up)
  * if you don't have checkin permissions, use the SF patch manager and note the patch number here (perhaps in the form of a link to python.org/sf/NNNNN), and add a note "FIXED" (plus name etc.)
  * if you fix a test, and you check in the fix, add a note "COMMITTED" with the svn revision (occasionally we'll clean these up)
  * if you don't have checkin permissions, use the SF patch manager and note the patch number here (perhaps in the form of a link to python.org/sf/NNNNN), and add a note "FIXED IN SF" (plus name etc.)
Line 14: Line 14:
  * Assume you've got the py3k-struni branch checked out
  * ./configure
  * make
  * ./python Lib/test/regrtest.py test_foobar
  * ./python Lib/test/test_foobar.py # for more detail about failures
Assume you've got the py3k branch checked out.
Line 20: Line 16:
== The tests == {{{
./configure
make
./python Lib/test/regrtest.py test_foobar # runs test_foobar
./python Lib/test/test_foobar.py # for more detail about failures
}}}
Line 22: Line 23:
test_aepack (Some tests need you to use {{{regrtest.py -uall}}} above.)
Line 24: Line 25:
test_applesingle ------
Line 26: Line 27:
test_asynchat = The Failing Tests =
Line 28: Line 29:
test_audioop   * test_email (CosminStejerean - at least some problems seem to be caused by base64MIME, problems with splitting headers into multiple lines - 08/08/07) (VictorStinner - imghdr and sndhdr, related modules, are now fixed) (MINE Barry Warsaw)
Line 30: Line 31:
test_bigmem   * test_email_codecs
Line 32: Line 33:
test_cProfile   * test_email_renamed (should we get rid of this, as it's about an old renaming?)
Line 34: Line 35:
test_cmd_line   * test_xmlrpc - started failing after merge of new code from trunk
Line 36: Line 37:
test_compile
Line 38: Line 38:
test_cookielib == Tests Failing Under Stress ==
Line 40: Line 40:
test_cpickle A few tests pass normally but fail when run by a debug build using {{{regrtest.py -R4:3:}}}. This runs the test 7 times to detect leaks. The following tests have problems under this mode:
Line 42: Line 42:
test_csv   * Confirmed failing tests:
Line 44: Line 44:
test_ctypes     * test_structmember
    * test_collections
    * test_runpy
    * test_asynchat (seems to hang in cleanup)
Line 46: Line 49:
test_descr   * Intermittent failures:
Line 48: Line 51:
test_dl     * test_gzip?
    * test_poplib? (Neal reported that it pegged the CPU)
    * test_mmap got a bus error when running -R 4:3: (also some test failures b/c I was running other tests and TESTFN was removed)
Line 50: Line 55:
test_doctest
Line 52: Line 56:
test_email == Tests Failing on Some Platforms Only ==
Line 54: Line 58:
test_email_codecs   * test_ossaudiodev (64-bit)
Line 56: Line 60:
test_email_renamed   * test_coding (cygwin and some gentoo) - UnicodeDecodeError: 'ascii' codec can't decode byte 0xe1 in position 105: ordinal not in range(128)
Line 58: Line 62:
test_frozen   * test_marshal (cygwin)
Line 60: Line 64:
test_ftplib   * test_normalization (gentoo) - same as test_coding. On the machine they fail on, locale.getlocale() is (None, None)
Line 62: Line 66:
test_genericpath   * test_codecs (OSX PPC) - probably a byte order issue in the new UTF-32 codec MINE Walter D.
Line 64: Line 68:
test_getargs === Other Conditional Failures ===
Line 66: Line 70:
test_gettext

test_hmac

test_macostools

test_mailbox

test_marshal

test_minidom

test_mmap

test_old_mailbox

test_pep263

test_pickle

test_pickletools

test_plistlib

test_poll

test_poplib

test_posixpath

test_pyexpat

test_quopri

test_resource

test_scriptpackages

test_sgmllib

test_shelve

test_socket

test_sqlite

test_tarfile

test_tcl

test_telnetlib

test_threaded_import

test_ucn

test_unicode_file

test_urllib

test_urllib2

test_uu

test_wave

test_xdrlib

test_xml_etree

test_xml_etree_c

test_xmlrpc

test_xpickle

test_zipimport

----
CategoryLanguage
  * test_shelve fails when the default database chosen by anydbm is bsddb. It works with dbm, gdbm and (presumably) with ndbm (all of which are very similar).

(Back to ["Python3000"].)

List of tests that are failing in the py3k branch

Protocol:

  • if you start working on a test, to avoid duplicate work, add your name+email+date to the bulleted item for the test below, with the text "MINE"
  • if you figure out why a test is failing, just add a note (name etc. is still appreciated)
  • if you fix a test, and you check in the fix, add a note "COMMITTED" with the svn revision (occasionally we'll clean these up)
  • if you don't have checkin permissions, use the SF patch manager and note the patch number here (perhaps in the form of a link to python.org/sf/NNNNN), and add a note "FIXED IN SF" (plus name etc.)

How to run tests

Assume you've got the py3k branch checked out.

./configure
make
./python Lib/test/regrtest.py test_foobar  # runs test_foobar
./python Lib/test/test_foobar.py   # for more detail about failures

(Some tests need you to use regrtest.py -uall above.)


The Failing Tests

  • test_email (CosminStejerean - at least some problems seem to be caused by base64MIME, problems with splitting headers into multiple lines - 08/08/07) (VictorStinner - imghdr and sndhdr, related modules, are now fixed) (MINE Barry Warsaw)

  • test_email_codecs
  • test_email_renamed (should we get rid of this, as it's about an old renaming?)
  • test_xmlrpc - started failing after merge of new code from trunk

Tests Failing Under Stress

A few tests pass normally but fail when run by a debug build using regrtest.py -R4:3:. This runs the test 7 times to detect leaks. The following tests have problems under this mode:

  • Confirmed failing tests:
    • test_structmember
    • test_collections
    • test_runpy
    • test_asynchat (seems to hang in cleanup)
  • Intermittent failures:
    • test_gzip?
    • test_poplib? (Neal reported that it pegged the CPU)
    • test_mmap got a bus error when running -R 4:3: (also some test failures b/c I was running other tests and TESTFN was removed)

Tests Failing on Some Platforms Only

  • test_ossaudiodev (64-bit)
  • test_coding (cygwin and some gentoo) - UnicodeDecodeError: 'ascii' codec can't decode byte 0xe1 in position 105: ordinal not in range(128)

  • test_marshal (cygwin)
  • test_normalization (gentoo) - same as test_coding. On the machine they fail on, locale.getlocale() is (None, None)
  • test_codecs (OSX PPC) - probably a byte order issue in the new UTF-32 codec MINE Walter D.

Other Conditional Failures

  • test_shelve fails when the default database chosen by anydbm is bsddb. It works with dbm, gdbm and (presumably) with ndbm (all of which are very similar).

Py3kStrUniTests (last edited 2008-11-15 14:00:38 by localhost)

Unable to edit the page? See the FrontPage for instructions.