[Python-checkins] buildbot warnings in hppa Ubuntu dapper trunk

Tim Peters tim.peters at gmail.com
Fri Jun 9 03:20:45 CEST 2006


[buildbot at python.org]
>> The Buildbot has detected a new failure of hppa Ubuntu dapper trunk.
>> Full details are available at:
>>
> http://www.python.org/dev/buildbot/all/hppa%2520Ubuntu%2520dapper%2520trunk/builds/603
>>
>> Buildbot URL: http://www.python.org/dev/buildbot/all/
>>
>> Build Reason:
>> Build Source Stamp: [branch trunk] HEAD
>> Blamelist: brett.cannon
>>
>> Build Had Warnings: warnings test

[brett.cannon, trying to weasle out ;-)]
> OK, I have no clue how my change could trigger this failure.  Anyone have a
> clue?

Note something from that log:  test_optparse originally failed in
test_filetype_noexist:

test test_optparse failed -- Traceback (most recent call last):
  File "/home/pybot/buildarea/trunk.klose-ubuntu-hppa/build/Lib/test/test_optparse.py",
line 1042, in test_filetype_noexist
    test_support.TESTFN)
  File "/home/pybot/buildarea/trunk.klose-ubuntu-hppa/build/Lib/test/test_optparse.py",
line 158, in assertParseFail
    self.assertFalse("expected parse failure")
AssertionError

But when test_optparse was re-run with -v, type_noexist passed, and
test_optparse failed in test_version instead.

OTOH, test_optparse's test_filetype_noexist _also_ failed on the "x86
W2k trunk" buildbot, build 992, with your rev 46757 alone in the
blamelist, and that makes it harder to swallow that the HPPA buildbot
is just flaky here.  On the W2k run, test_optparse also passed (all of
it) when it got rerun with -v.

If there's "a real reason" for this, it may well require running some
subset of tests in a specific order.  Alas, since your patch changed C
code, it's potentially to blame for any kind of failure whatsoever.

I forced another test run on the HPPA box just to see what happens.

I'm also running the tests on my box in exactly the same order the W2k
box ran them during its test_optparse failure.   Oops!  That finished
already, and test_optparse _did_ fail here.  I'll attach the list of
tests it ran.  You use this by passing it to regrtest.py's "-f"
argument.  Next step is binary-search'ish to get a minimal set of
failing tests.

Happily, I forgot to use -uall, so the 4 skipped tests here can be
removed at once:

$ python_d  -E -tt ../lib/test/regrtest.py -f f.txt
test_distutils
...
test_optparse
test test_optparse failed -- Traceback (most recent call last):
  File "C:\Code\python\lib\test\test_optparse.py", line 1042, in
test_filetype_noexist
    test_support.TESTFN)
  File "C:\Code\python\lib\test\test_optparse.py", line 158, in assertParseFail
    self.assertFalse("expected parse failure")
AssertionError

135 tests OK.
1 test failed:
    test_optparse
4 tests skipped:
    test_largefile test_socket_ssl test_timeout test_urllibnet
Those skips are all expected on win32.
-------------- next part --------------
test_distutils
test_capi
test_fpformat
test_compare
test_sax
test_bz2
test_with
test_functools
test_sets
test_stringprep
test_grammar
test_wave
test_fnmatch
test_minidom
test_iter
test_urllibnet
test_compile
test_threaded_import
test_peepholer
test_asynchat
test_set
test_StringIO
test_urlparse
test_doctest2
test_slice
test_module
test_decimal
test_htmllib
test_xml_etree
test_imp
test_call
test_csv
test_unittest
test_anydbm
test_audioop
test_email_codecs
test_datetime
test_ntpath
test_types
test_filecmp
test_exception_variations
test_coding
test_new
test_urllib2
test_syntax
test_inspect
test_xdrlib
test_codecencodings_tw
test_traceback
test_defaultdict
test_hotshot
test_textwrap
test_MimeWriter
test_socket_ssl
test_imaplib
test_tuple
test_codeccallbacks
test_time
test_unpack
test_string
test_array
test_locale
test_long_future
test_getargs2
test_augassign
test_fileinput
test_softspace
test_scope
test_codecmaps_cn
test_charmapcodec
test_pyexpat
test_genexps
test_runpy
test_userstring
test_bsddb
test_binhex
test_urllib
test_startfile
test_repr
test_quopri
test_timeout
test_weakref
test_codecs
test_structseq
test_warnings
test_frozen
test_email_renamed
test_shlex
test_codecmaps_tw
test_coercion
test_largefile
test_codecencodings_kr
test_pprint
test_dummy_threading
test_global
test_platform
test_mimetypes
test_cProfile
test_complex
test_bastion
test_getopt
test_tcl
test_strftime
test_copy
test_unicode
test_symtable
test_bufio
test_pep263
test_zlib
test_zipfile
test_zipimport
test_code
test_pkgimport
test_winsound
test_macpath
test_profilehooks
test_pickletools
test_mailbox
test_bool
test_funcattrs
test_calendar
test_multibytecodec
test_select
test_trace
test_math
test_str
test_pyclbr
test_pickle
test_site
test_pkg
test_bisect
test_userdict
test_univnewlines
test_compiler
test_rfc822
test_unicode_file
test_file
test_threadedtempfile
test_class
test_optparse



More information about the Python-checkins mailing list