![[Buildbot Logo]](/chrome/site/header-text-transparent.png)
Ticket #601 (closed defect: fixed)
builds "disappear" when a two builders share a slave (with lock?)
| Reported by: | ddunbar | Owned by: | |
|---|---|---|---|
| Priority: | major | Milestone: | undecided |
| Version: | 0.7.11 | Keywords: | |
| Cc: | daniel@… |
Description
I have a BuildBot setup where I have multiple builders which share a slave, and I use a slave lock to prevent the slave from building both at once (I use a lock instead of max builds because I seemed to get fairer results that way, maybe this has been fixed?).
Sometimes the build results in the waterfall for one of the two builds will disappear, when the slave is currently running the other builder. I'm not sure if this always happens, and it only seems to happen when the builder is building.
I'd like to fix this, but don't really know where to start looking. I'd appreciate it if someone could point me in the right direction.
Change History
comment:2 Changed 4 years ago by ddunbar
Ok, I found the problem. It occurs when two builders share a slave, with a slave lock. If two builds run at the same time, then the builder which is locked starts returning None for getBuild(-1). The event generator (and console, fwiw) just stop searching for builds at that point, so everything disappears.
I worked around this by just adding hacks to the event generator and console to keep looking if the head build is None, but I don't think thats the right approach.