[Buildbot-devel] "but we weren't running, quitting silently" error message

[Damian Krzeminski]

Brian Warner wrote:
> Damian Krzeminski <damian at pingtel.com> writes:
> 
>> My buildslaves seem to get stuck from time to time with
>> "SlaveBuilder.commandComplete <> but we weren't running, quitting
>> silently". Usually it happens when executing "svnversion" command of
>> standard SVN step.
> 
>> But restarting the slave seem to be the only way to unstuck the build.
> 
>> Is this a known problem? If someone has a better workaround than restarting
>> the slave please let me know.
> 
> I've been having the same problem recently. It always seems to happen right
> after I've reconfigured that buildslave (by modifying something in the
> master.cfg file and then SIGHUPing the buildmaster). Part of the reconfigure
> process is to forcibly detach the buildslave and then make it reattach. I
> suspect that the old (now inactive) SlaveBuilder is sticking around, and gets
> used for the next build instead of the new (and active) instance.
> 
> The only workaround I've been able to come up with is the one you found:
> restarting the buildslave.
> 
> Are you seeing this happen without a reconfiguration event? That might
> indicate the bug is somewhere else.
> 
> This bug is high on my priority list, as it's starting to get really annoying
> to me at work :).
> 
> cheers,
>  -Brian
> 

I think you are right: it does happen after I reconfigure the master. I just started using buildbot 
and I was reconfiguring it pretty often. I guess that's why I did not notice the connection.
Thanks!
Damian