[Buildbot-devel] buildbot sighup master leaves builders in disconnected state

[Elliot Murphy]

I was trying out the buildmaster sighup command (to force the build master
to re-read the configuration file), and I think I've found a bug. The
waterfall display shows that the configuration was updated, and shows
disconnect/connect messages for each of the build slaves. When I look at the
log for the build slaves, there are messages for "removing old builder" and
"message from master: attached". However, when I got to force a build on one
of the slaves, the status shows as not connected, so only the ping button is
available.

 

Restarting the build slaves fixes things, but it seemed like the point of
buildbot sighup was to avoid needing to touch the slaves when updating a
configuration.

 

 

regards,

-elliot

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://buildbot.net/pipermail/devel/attachments/20041111/1a4ceca3/attachment.html>