[Buildbot-devel] Programmatic Slave status

[Dustin J. Mitchell]

On Mon, Feb 10, 2014 at 3:48 PM, Mick Jordan <mick.jordan at oracle.com> wrote:
> This seems to be related to whether I reconfig rather that restart the
> buildbot after making changes to master.cfg.

Ah, interesting.  Because BuildSlave instances are so closely tied to
the current master/slave protocol, on a reconfig we do this weird
"consume the soul of your successor" operation, where the *old*
BuildSlave instance tries to copy all of the attributes of the new
BuildSlave instance and continue operating.  That's been the source of
lots of weird bugs similar to this one.

Dustin