[Python-Dev] [Python-checkins] buildbot warnings in hppa Ubuntu dapper trunk
brett at python.org
Fri Jun 9 04:30:55 CEST 2006
On 6/8/06, Tim Peters <tim.peters at gmail.com> wrote:
> FYI, here's the minimal set of failing tests:
> $ python_d ../Lib/test/regrtest.py test_file test_optparse
> test test_optparse failed -- Traceback (most recent call last):
> File "C:\Code\python\lib\test\test_optparse.py", line 1042, in
> File "C:\Code\python\lib\test\test_optparse.py", line 158, in
> self.assertFalse("expected parse failure")
Different type of failure as well; if you look at the original failure it
has to do with the help output having an extra newline.
1 test OK.
> 1 test failed:
> [23476 refs]
> That also, using -w and -f, reproduces the bizarre HPPA behavior when
> test_optparse is rerun in verbose mode (test_filetype_noexist passes
> then, but test_version fails).
> I have no idea why any of this is true, but there's good and bad news:
> reverting rev 46757 does _not_ make the problem go away.
Actually, that run had two checkins; there was also 46755. But when I ``svn
update -r46754`` it still fails on my OS X laptop. So still ain't my
> off the hook, but we don't know who to crucify in your place ;-)
Oh, we live in America; we have a list to pull from. =)
As to why the failure only showed up recently, I'm not sure, but
> test_file must run before test_optparse, and it looks like the problem
> goes away if "too many"(!) other tests intervene. The Win2K buildbot
> is unique in that test_file has been followed very soon by
> test_optparse two builds in a row.
We don't have any mechanism in place to record when we find tests failing in
a row to always run them in that order until we fix it, do we? Nor do we
have a script to just continually check out older revisions in svn, compile,
and test until the tests do pass, huh?
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Python-Dev