Indeed, this is an old bug namely the builder global status is not
correclty tracked under some condition.
Nobody actually got the chance of fixing it (yet) as it is mostly harmless,
and probably hard to reproduce/fix
This bug is not present in nine as there is no builder status (ahah)
Le jeu. 22 sept. 2016 à 01:40, Dan Kegel <d...@kegel.com> a écrit :
> Hey folks,
> still using 0.8-ish.
> Just now I restarted the buildmaster process, and four of my active
> became zombies. They were dead, but the status showed them as half-alive.
> All slaves were up and idle, but the four builders were yellow, with no
> and had no stop button! Clicking 'force build' happily built and erased
> the odd yellow status.
> So evidently it's a harmless state due to buildbot not properly flushing
> the stopped status of all builds to disk when stopping the master?
> This master is still using sqlite in spite of being a big instance
> that really should
> be using a real database.
> Satisfying to have caught it in the act this time (this has happened a
> dozen times
> before, but in more confusing circumstances).
> users mailing list
users mailing list