martin v löwis qpnyslvloewisde trent nelson wrote thatll kill first python_dexe instance finds matching given path given buildbots run trunkrelease25maintpy3k parallel thats actually given currently dont run multiple builds simultaneously slave thought slave lock applied per branch per host name suggests per slave slave namepassword pair along buildbottac file sequencing builds per builder locking mechanism actually single builder wont schedule new build long build already running currently three builders per slave serialized slave lock hence occasional long sequences yellow build nnn build starts tries acquire slave lock different builder still holds machine understand also two slaves running might principle kill others python_dexe processes except paths different amd64 vs regards martin _______________________________________________ pythondev mailing list zvlllneumpythonorg httpmailpythonorgmailmanlistinfopythondev unsubscribe httpmailpythonorgmailmanoptionspythondevpythondev40tangomucom thu 07 aug 2008 075108 0200 pythondev toolsbuildbotkill_pythonc cant helping cause