Differences between revisions 3 and 5 (spanning 2 versions)
Revision 3 as of 2007-07-10 14:06:53
Size: 1907
Editor: 213
Comment:
Revision 5 as of 2007-07-10 20:43:48
Size: 2229
Editor: 216
Comment: update based on re-running all tests on ubuntu
Deletions are marked like this. Additions are marked like this.
Line 22: Line 22:
test_aepack test_aepack (OSX only)
Line 24: Line 24:
test_applesingle test_applesingle (OSX only)
Line 32: Line 32:
test_cProfile test_cProfile: not worth it? (I think this will be killed)
Line 40: Line 40:
test_cpickle test_cpickle: not worth it? (I think this may be killed.)
Line 58: Line 58:
test_file (fails on Ubuntu, passes on OSX?!)
Line 66: Line 68:
test_hmac

test_macostools
test_macostools (OSX only)
Line 71: Line 71:

test_marshal
Line 84: Line 82:
test_plistlib test_plistlib (OSX only)
Line 89: Line 87:

test_posixpath
Line 98: Line 94:
test_scriptpackages test_scriptpackages (OSX only)
Line 100: Line 96:
test_sgmllib test_sgmllib (passes on Ubuntu, fails on OSX)
Line 103: Line 99:

test_socket
Line 112: Line 106:
test_telnetlib
Line 120: Line 112:
test_urllib test_urllib2
Line 122: Line 114:
test_urllib2 test_urllib2_localnet
Line 126: Line 118:
test_wave test_uuid (passes on OSX, fails on Ubuntu)

test_wave: probably not worth fixing; aren't we going to delete this?
Line 138: Line 132:
test_zipimport test_zipimport: lots of str/bytes issues, shouldn't be too hard; important

List of tests that are failing in the py3k-struni branch

(Back to ["Python3000"].)

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 "FIXING" or "INVESTIGATING"
  • 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 "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.)

How to run tests

  • 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

The tests

test_aepack (OSX only)

test_applesingle (OSX only)

test_asynchat

test_audioop

test_bigmem

test_cProfile: not worth it? (I think this will be killed)

test_cmd_line

test_compile

test_cookielib

test_cpickle: not worth it? (I think this may be killed.)

test_csv

test_ctypes

test_descr

test_dl

test_doctest

test_email

test_email_codecs

test_email_renamed

test_file (fails on Ubuntu, passes on OSX?!)

test_frozen

test_ftplib

test_getargs

test_gettext

test_macostools (OSX only)

test_mailbox

test_minidom

test_mmap

test_old_mailbox

test_pep263

test_pickletools

test_plistlib (OSX only)

test_poll

test_poplib

test_pyexpat

test_quopri

test_resource

test_scriptpackages (OSX only)

test_sgmllib (passes on Ubuntu, fails on OSX)

test_shelve

test_sqlite

test_tarfile

test_tcl

test_threaded_import

test_ucn

test_unicode_file

test_urllib2

test_urllib2_localnet

test_uu

test_uuid (passes on OSX, fails on Ubuntu)

test_wave: probably not worth fixing; aren't we going to delete this?

test_xdrlib

test_xml_etree

test_xml_etree_c

test_xmlrpc

test_xpickle

test_zipimport: lots of str/bytes issues, shouldn't be too hard; important


CategoryLanguage

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

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