[Python-Dev] Still looking for volunteer to run Windows buildbot

Jean-Paul Calderone exarkun at divmod.com
Wed Mar 15 16:15:44 CET 2006

On Wed, 15 Mar 2006 00:00:06 -0500, Tim Peters <tim.peters at gmail.com> wrote:
>[Trent Mick]
>> Yes I've noticed it too. I've had to kill python_d.exe a few times. I
>> haven't yet had the chance to look into it. I am NOT getting this error
>> on another Windows Python build slave that I am running in-house for
>> play.
>The last run on your Win2K slave that got beyond the compile step:
>Looks like it was running test_bsddb at the time, and the test
>framework gave up after waiting 20 minutes for more output.  I had one
>of those "recently" that waited 20 minutes for output after starting
>test_shelve, but it's scrolled off the page.  Berkeley DB is fishy.
>Looks like the buildbot doesn't know how to kill a process on Windows
>either (SIGKILL sure ain't gonna do it ;-)).

It should actually be using TerminateProcess (depending on the Twisted version being used, the relevant code is either in twisted/internet/_dumbwin32proc.py or twisted/internet/win32eventreactor.py, in the signalProcess method in either case), but even this doesn't seem to be a completely reliable way to end a process.  Twisted's buildbot has run into this problem as well, but we haven't figure out how to fix it yet.  Suggestions welcome - patches even more so :)


More information about the Python-Dev mailing list