[Buildbot-devel] Catching an exception when a slave is expected to disconnect

[Charles Lepple]

I have a test case in one of my builders where I would like to run
some code on a slave, but at the end of the build, I want to reboot
the slave system (to ensure a clean slate for the next test).

Through some combination of scheduling the reboot for some time in the
future, and having a MasterShellCommand run "sleep" while the slave
disconnects and reboots, things kinda-sorta worked in 0.8.2
(master-side; I think it was 0.8.3 on the slave side).

After upgrading to 0.8.3 on the master, the disconnection turns into
an exception, which results in the same build being retried after the
slave reconnects. (I certainly see this as being useful in the general
case, but we would like to somehow override this such that
disconnection is expected, or at least not a problem, in the reboot
step.)

Before I dive too deeply into the master-side disconnection handling
code, has anyone else encountered a similar situation?

Thanks,

-- 
- Charles Lepple