[Python-Dev] [Windows, buildbot] kill_python.c mystery (original) (raw)

"Martin v. Löwis" martin at v.loewis.de
Thu Jul 27 08:32:39 CEST 2006

Tim Peters wrote:

Today I noticed this happened when the buildbot started to run tests, and I'm 100% sure it's due to this code in Tools/buildbot/killpython.c

Didn't you know that you signed in to run arbitrary viruses, worms, and trojan horses when you added your machine to the buildbot infrastructure :-? You just haven't seen buildbot erasing your hard disk and filling your coffee machine with tea, yet.

(strstr(path, "build\python.exe") != NULL)) { Why is the second clause there?

That's for Cygwin (i.e. Anthony Baxter's machine). As Neal suggests, preceding the executable path with another backslash should solve this problem.

As a related note, this entire approach will also manage to kill python.exe from an unrelated buildbot installation, e.g. a 2.4 build job might kill python.exe from the trunk. This actually helped when I tried to get the Cygwin slave to get unstuck, and shouldn't do harm since we currently don't run to builds on the same slave simultaneously, but could be surprising when parallel builds are activated some day.

Sorry for messing with your machine,

Martin

More information about the Python-Dev mailing list