The Windows 7 buildbots are failing on test_asdl_parser, but I have no idea why – the test works for me just fine. Yury and Benjamin made the most recent changes to Python.asdl, but I have no idea what effect they would have here, or why it’s Windows only.
The WS2K3 machine needs a reboot – I pinged Trent about that months ago – and the XP one isn’t supported for 3.5.
Pending the test_asdl_parser fix, I’d also like to see AMD64 Windows 8 (http://buildbot.python.org/all/builders/AMD64%20Windows8%203.x) be promoted to stable, as it’s one of only two currently using the right compiler.
Coming to PyData Seattle 2015http://conf.pydata.org/seattle2015/? Hosted by Microsoft on our Redmond campus, July 24-26
From: python-committers [mailto:email@example.com] On Behalf Of Larry Hastings Sent: Friday, May 22, 2015 1444 To: Python Dev; python-committers Subject: [python-committers] Can we clean up the buildbots please?
Right now we have eight online buildbots for Python trunk. Of those, currently *six* are reporting errors in either the compile or test phases. http://buildbot.python.org/all/waterfall?category=3.x.stable There's one platform ("AMD64 Snow Leop") where the failures are sporadic "stack overflow" errors encountered during the test suite. But the other five platforms have consistent failures, build after build. Those platforms: AMD64 OpenIndiana AMD64 Windows7 SP1 x86 Windows Server 2003 [SB] x86 Windows7 x86 XP-4 That includes *all* of the Windows buildbots.
Gosh, it sure would be nice if Beta 1 didn't fail on Windows, wouldn't it? Could some Windows core devs take a look at the failures and see about cleaning them up?
Naturally the OpenIndiana and OS X devs are invited to fix the errors on those platforms too,
p.s. My apologies for not bringing attention to this sooner. But, well, we still have a day left, right?