[Python-Dev] [Python-checkins] buildbot warnings in hppa Ubuntu dapper trunk (original) (raw)
Brett Cannon brett at python.org
Fri Jun 9 04:30:55 CEST 2006
- Previous message: [Python-Dev] [Python-checkins] buildbot warnings in hppa Ubuntu dapper trunk
- Next message: [Python-Dev] [Python-checkins] buildbot warnings in hppa Ubuntu dapper trunk
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On 6/8/06, Tim Peters <tim.peters at gmail.com> wrote:
FYI, here's the minimal set of failing tests: $ pythond ../Lib/test/regrtest.py testfile testoptparse testfile testoptparse test testoptparse failed -- Traceback (most recent call last): File "C:\Code\python\lib\test\testoptparse.py", line 1042, in testfiletypenoexist testsupport.TESTFN) File "C:\Code\python\lib\test\testoptparse.py", line 158, in assertParseFail self.assertFalse("expected parse failure") AssertionError
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: testoptparse [23476 refs]
That also, using -w and -f, reproduces the bizarre HPPA behavior when testoptparse is rerun in verbose mode (testfiletypenoexist passes then, but testversion 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
fault. =)
So you're
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
testfile must run before testoptparse, and it looks like the problem goes away if "too many"(!) other tests intervene. The Win2K buildbot is unique in that testfile has been followed very soon by testoptparse 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?
-Brett -------------- next part -------------- An HTML attachment was scrubbed... URL: http://mail.python.org/pipermail/python-dev/attachments/20060608/57f96165/attachment.htm
- Previous message: [Python-Dev] [Python-checkins] buildbot warnings in hppa Ubuntu dapper trunk
- Next message: [Python-Dev] [Python-checkins] buildbot warnings in hppa Ubuntu dapper trunk
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]