Trent Nelson wrote: >>> That'll kill the first python_d.exe instance it finds matching the >>> given path; given that our buildbots run trunk/release25-maint/py3k >>> in parallel >> That's actually not a given: we currently *don't* run multiple builds >> simultaneously on the same slave. > > I thought the slave lock only applied per branch, not per host?
As the name suggests, it's per slave :-) a slave being the name/password pair, along with the buildbot.tac file. The sequencing of builds per builder is not a locking mechanism, actually; a single builder just won't schedule a new build as long as a build is already running. So we have currently three builders per slave, and these are serialized with the slave lock (hence the occasional long sequences of yellow "Build nnn": the build starts, tries to acquire the slave lock, which then a different builder still holds). Now, on your machine, I understand you also have two slaves running. They might, in principle, kill each other's python_d.exe processes, except that the paths will be different there (amd64 vs. not). Regards, Martin _______________________________________________ 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
