[issue25848] Tkinter tests failed on Windows buildbots

Zachary Ware added the comment: I added the note to the devguide instead of pep101, and will be removing the 3.4 builders shortly. -- resolution: -> out of date stage: -> resolved status: open -> closed ___ Python tracker

[issue25848] Tkinter tests failed on Windows buildbots

Roundup Robot added the comment: New changeset 5430f4fd4ca7 by Zachary Ware in branch 'default': Issue #25848: Add section on running a build on all custom builders https://hg.python.org/devguide/rev/5430f4fd4ca7 -- nosy: +python-dev ___ Python tracke

[issue25848] Tkinter tests failed on Windows buildbots

Zachary Ware added the comment: I think only keeping some builders would be more complex than any other option. Here's a patch against pep101 to document the custom builder trick. -- keywords: +patch Added file: http://bugs.python.org/file41389/pep101_custom_buildbots.diff ___

[issue25848] Tkinter tests failed on Windows buildbots

R. David Murray added the comment: How about just keeping the stable set configs, minus any from that set that have special cases? Although if it is just one form submission, maybe we just need to document that in the release manager's guide? -- __

[issue25848] Tkinter tests failed on Windows buildbots

Zachary Ware added the comment: Would pretty much eliminate the benefit; there are currently a few special cases for 3.4 (particularly for the ICC builders, and the XP bot), which could go away. For the record, the secret undocumented method for running a build on all custom builders is to fi

[issue25848] Tkinter tests failed on Windows buildbots

R. David Murray added the comment: Well, it clutters up the buildbot web interface with builders that aren't being used. Our historical pattern has been to deactivate the builders after a release goes into security-fix-only mode. Zach, would it be practical to just comment them out and then r

[issue25848] Tkinter tests failed on Windows buildbots

Larry Hastings added the comment: I hear your plea. But isn't it almost as easy to just leave it alone? 3.4 won't get many checkins from now on, so it won't actually kick off many tasks. But it would mean the "check the buildbots" step of making a release would be super easy, rather than th

[issue25848] Tkinter tests failed on Windows buildbots

Zachary Ware added the comment: Larry: considering that 3.4 is now officially out of bugfix mode, how long do you want to keep the 3.4 buildbots around? From a selfish buildmaster configurator perspective, axing the 3.4 bots simplifies a few things :) -- _

[issue25848] Tkinter tests failed on Windows buildbots

Larry Hastings added the comment: I'm assuming this is a configuration issue on the buildbots. -- priority: release blocker -> low ___ Python tracker ___

[issue25848] Tkinter tests failed on Windows buildbots

Steve Dower added the comment: I was encountering this recently trying to set up a build machine for the release, and it seems to be a build issue. Martin is building the release and apparently has it working. -- nosy: +loewis ___ Python tracker

[issue25848] Tkinter tests failed on Windows buildbots

New submission from Serhiy Storchaka: Tkinter related tests are failed on 4 of 6 Windows 3.4 buildbots. http://buildbot.python.org/all/builders/AMD64%20Windows7%20SP1%203.4/builds/1418/steps/test/logs/stdio http://buildbot.python.org/all/builders/AMD64%20Windows10%203.4/builds/220/steps/test/log