aakashjain has quit [Remote host closed the connection]
aakashjain has joined #buildbot
aakashjain has quit [Ping timeout: 250 seconds]
aakashjain has joined #buildbot
aakashjain has quit [Ping timeout: 240 seconds]
aakashjain has joined #buildbot
aakashjain has quit [Remote host closed the connection]
aakashjain has joined #buildbot
aakashjain has quit [Remote host closed the connection]
iomartin has joined #buildbot
mjw has quit [Killed (NickServ (GHOST command used by markw!~wielaard@gnu.wildebeest.org))]
wielaard has joined #buildbot
<iomartin>
Hello! I have a couple of questions about latent workers, in particular the libvirt worker. The first one is about the build_wait_timeout parameter. If I set it to 0, does it mean that the worker will always shutdown after each build (regardless if there are pending builds) or does it mean that it will only shutdown if there are no pending builds?
<iomartin>
The second question is if there is a way to have latent workers be mutually exclusive. The setup we have in mind has several VMs in the same host, and I have one piece of HW that needs to be passedthrough to the VM. This means that they can't all start at the same time, only one can be up at a time. Kind of like max_builds but that can be applied
<iomartin>
to several workers
aakashjain has joined #buildbot
iomartin has quit [Quit: Client closed]
iomartin has joined #buildbot
iomartin has quit [Quit: Client closed]
iomartin has joined #buildbot
dustinm` has quit [Quit: Leaving]
iomartin has quit [Quit: Client closed]
aakashjain has quit [Remote host closed the connection]
dustinm` has joined #buildbot
mjw has joined #buildbot
<mjw>
Is there a way to see the "state" of a (latent) worker?
<mjw>
I have two latent workers which are never selected to run any jobs
<mjw>
Both had a couple of issues with instantiating their image a while back
<mjw>
I am guessing that caused them to be put into some "broken" state and so are now never selected to do a build