<br><br><div><span class="gmail_quote">On 6/8/06, <b class="gmail_sendername">Tim Peters</b> <<a href="mailto:tim.peters@gmail.com" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">tim.peters@gmail.com
</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
FYI, here's the minimal set of failing tests:<br><br>$ python_d ../Lib/test/regrtest.py test_file test_optparse<br>test_file<br>test_optparse<br>test test_optparse failed -- Traceback (most recent call last):<br> File "C:\Code\python\lib\test\test_optparse.py", line 1042, in
<br>test_filetype_noexist<br> test_support.TESTFN)<br> File "C:\Code\python\lib\test\test_optparse.py", line 158, in assertParseFail<br> self.assertFalse("expected parse failure")<br>AssertionError
</blockquote><div><br>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.<br> </div><br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
1 test OK.<br>1 test failed:<br> test_optparse<br>[23476 refs]<br><br>That also, using -w and -f, reproduces the bizarre HPPA behavior when<br>test_optparse is rerun in verbose mode (test_filetype_noexist passes<br>then, but test_version fails).
<br><br>I have no idea why any of this is true, but there's good and bad news:<br> reverting rev 46757 does _not_ make the problem go away.</blockquote><div><br>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. =)
<br> </div><br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
So you're<br>off the hook, but we don't know who to crucify in your place ;-)</blockquote><div><br>Oh, we live in America; we have a list to pull from. =) <br></div><br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
As to why the failure only showed up recently, I'm not sure, but<br>test_file must run before test_optparse, and it looks like the problem<br>goes away if "too many"(!) other tests intervene. The Win2K buildbot
<br>is unique in that test_file has been followed very soon by<br>test_optparse two builds in a row.<br></blockquote></div><br>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?
<br><br>-Brett<br>