Opened 5 years ago

Last modified 3 years ago

#3170 new defect

If a latent slave spontaneously disconnects, buildbot will never try to start it.

Reported by: tom.prince Owned by:
Priority: major Milestone: 0.9.+
Version: Keywords: latent


It appears this has something to do with buildbot thinking the slave is then disconnected, not latent.

Change History (5)

comment:1 Changed 5 years ago by dustin

  • Milestone changed from undecided to 0.9.0
  • Type changed from undecided to defect

Do you have logs or a repro recipe or something more concrete?

comment:2 Changed 5 years ago by tom.prince

  1. Have a buildbot with a latent slave.
  2. Trigger a build that starts the slave.
  3. Outside of buildbot, shutdown the slave, or otherwise forcibly disconnect it (destroy the VM).
  4. Trigger another build that should start the slave, and notice that the latent slave never starts.

I haven't done this, but:

  1. Login via manhole, notice that the associated slavebuilder is disconnected, not LATENT.

comment:3 Changed 5 years ago by dustin

  • Version 0.8.10 deleted

comment:4 Changed 5 years ago by dustin

  • Keywords latent added
  • Milestone changed from 0.9.0 to 0.9.+
Note: See TracTickets for help on using tickets.