On Wed, 15 Mar 2006 00:00:06 -0500, Tim Peters <[EMAIL PROTECTED]> 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: > >http://www.python.org/dev/buildbot/all/x86%20W2k%20trunk/builds/16/step-test/0 > >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 :) Jean-Paul _______________________________________________ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
