[Python-Dev] Buildbot slave locks (Was: 2.5a1 Performance) (original) (raw)
"Martin v. Löwis" martin at v.loewis.de
Thu Apr 6 08:09:32 CEST 2006
- Previous message: [Python-Dev] 2.5a1 Performance
- Next message: [Python-Dev] Possible issue with 2.5a1 Win32 binary
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Brian Warner wrote:
I don't know what the python buildbot's master.cfg looks like, but you'll probably want to add something like this (taken from the buildbot.texinfo user's manual)
Thanks, I have now done that, and it seems to work. It would be nice if the builder status would indicate that it is waiting for a lock.
The name of the lock is meant for debugging, so you can tell why a given builder is stalled. Each buildslave gets its own lock, and the builder claims every lock listed in the 'locks' key before starting.
It wasn't first clear to me what "each buildslave gets its own lock"; I assumed it was my job to create a lock for each buildslave. I only then found out that a SlaveLock is always per slave (unlike a master lock, which is for the entire installation).
Regards, Martin
- Previous message: [Python-Dev] 2.5a1 Performance
- Next message: [Python-Dev] Possible issue with 2.5a1 Win32 binary
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]