[Buildbot-devel] Dead job permanently yellow?

[Dan Kegel]

One more symptom: two slaves are unhappy about a stray lock file:

fatal: Unable to create
'/home/buildbot/slave-state/ubu1204/g-speak-buildhost04-ubu1204/staging-ubu1204-master/source/.git/index.lock':
File exists.

Could restarting the server in the middle of a git step do that?

The slave in question is running buildbot-slave-0.8.7.
- Dan

On Fri, Mar 20, 2015 at 9:45 AM, Dan Kegel <dank at kegel.com> wrote:
> So... our buildbot got in that nasty state again where:
> - the waterfall shows a builder as yellow
> - clicking on the build shows it as yellow (with revision ??, since it
> failed during git step)
> - no buildslave is yellow, all are idle
>
> Forcing a new build that then fails does leave the builder red, but
> the old yellow job (on a different slave) is still there.
> Restarting the master doesn't help.
> Rebooting the slave doesn't help.
>
> Everything is normal otherwise.   Even if I disable all other slaves, the
> slave with the false yellow job still accepts new jobs properly.
>
> I guess I can just ignore the problem, but it feels a little funny.
>
> I think I triggered this by restarting the master while the slave was
> in the middle of a git step.