[Buildbot-devel] Some questions/problems running latest build bot source on Windows

Elliot Murphy elliot.murphy at veritas.com
Tue Nov 9 19:47:54 UTC 2004

|Yeah, spawnProcess() is an absolute necessity for the buildslaves. I
|the existing w32 slaves are using the 'win32' reactor, which does implement
|it, so it should be a simple matter of running the slaves under twistd with
|the '-r win32' argument (which I think the 'buildbot' script currently
|You can also run the unit tests under a different reactor by using the same
|argument. Give that a try and see if the ShellCommand failures go away.

This is great news! Now that you mention it, I remember seeing the buildbot
command use that argument, but I didn't make the connection.

Trying this command:
trial -o -r win32 buildbot.test

I see the tests hang at:
testSlave (buildbot.test.test_run.Status)
and consume a *lot* of CPU. Interrupting the test with CTRL-C, the stack
trace ends up down in win32eventreactor.py, doWaitForMultipleEvents.

Is there a way for me to comment out this test so that I can see if the
others pass?

|Alternately, you can grab the latest Twisted from the SVN repository and
|the buildbot against that. I've done this from time to time and I think
|everything should work.. there are a handful of DeprecationWarnings, but
|that's nust noise. I've been waiting until twisted-2.0 is released before
|addressing them, because some of the fixes would make Buildbot incompatible
|with Twisted-1.3.0 (and being incompatible with the only official release
|would be a drag).
Cool. It's good to know that is an option also, I'll probably try that out
when I get a little more time.


More information about the devel mailing list