I was wondering if an additional Windows buildbot would be helpful, in particular for py3k? If so, I should be able to run one, and wanted to request a buildbot account, as mentioned on the buildbot page on <a href="http://python.org">
python.org</a>. I've got some idle hardware - nothing fancy (x86 P4, 2.8GHz) but it's up and infrequently used, with a solid broadband connection.<br><br>I had some time to test, so set up a Windows XP SP2 virtual machine with all the various pieces needed for a buildbot. The host machine happens to run XP too, but using a virtual machine was a bit cleaner (including easy relocation over time if needed). I've manually done full builds of Python
2.5.1 (from release25-maint), 2.6a0 (from trunk), and 3.0x (from py3k) using the buildbot build and test batch files under tools, so I think the environment is good. 2.5.1 tested clean, 2.6a0 had two errors in test_ssl and test_winreg but they match some existing buildbots. The
3.0 tests are ugly, including a NULL pointer debug assertion triggered in test_os that kills the test run, but I'm assuming that's just the current state of 3.0. I've lurked on 3000-devel, but am not intimately up to date on expected behavior under Windows.
<br><br>Anyway, if it would be useful, I figured I could use this virtual machine for a buildbot for at least trunk and 3k, perhaps with 2.5 too. Not sure if that requires multiple accounts, or if you configure each buildbot instance with an SVN path (I didn't see anywhere obvious for the latter).
<br><br>-- David<br><br><br>