[Python-Dev] Status of 2.7b1?

[Brian Curtin]

On Sat, Apr 10, 2010 at 10:51, Nick Coghlan <ncoghlan at gmail.com> wrote:

> The trunk's been frozen for a few days now, which is starting to cut
> into the window for new fixes between b1 and b2 (down to just under 3
> weeks, and that's only if b1 was ready for release today).
>
> Is work in train to address or document the remaining buildbot failures
> (e.g. test_os on Windows [1]). At what point do we decide to document
> something as a known defect in the beta and release it anyway?
>
> (My question is mostly aimed at Benjamin for obvious reasons, but it
> would be good to hear from anyone that is actually looking into the
> Windows buildbot failure)
>
> Cheers,
> Nick.
>
> [1]
>
> http://www.python.org/dev/buildbot/trunk/builders/x86%20XP-4%20trunk/builds/3380/steps/test/logs/stdio
>
>
I contacted David Bolen for some details about the his buildbot because I
can't reproduce the failure on any Windows XP, Server 2003, or 7 box that I
have, and it's also not a problem on the other XP buildbot. He's traveling
at the moment but will try to get me access to the box after the weekend is
over.

When manually running test_os how buildbot runs it (via test.bat, which runs
rt.bat) he sees the failure. When running the test on a clean checkout
outside of how buildbot does anything, he doesn't see the failure. I'll try
to get access to figure out what the difference is.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/python-dev/attachments/20100410/a2883534/attachment.html>