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
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4