Tim Peters wrote:
I'm not sure how they get into such a state (but saw it at Zope Corp at times too). It's possible that their buildbot processes need to be restarted, and/or that the master process needs to be restarted.
It's a buildbot 0.7.1 bug (according to the 0.7.2 changelog); the sighup command sometimes gets confused. I thought it would survive the configuration change when no build is ongoing, but apparently I was wrong.