[users at bb.net] Triggered builds getting skipped
tardyp at gmail.com
Thu Apr 14 19:19:42 UTC 2016
I would suggest to upgrade to beta8
It contains this fix:
Which can lead to exceptions is nextWorker callback to be completely
ignored, and buildrequests not claimed.
If the problem persists, I would suggest to create a trac, and append the
result of the rest api like
This will tell the list of pending buildrequests, to see if there are
claimed or not.
We can then have the evidence if the problem comes in the buildrequest
distributor, or in the build subsystem.
Le jeu. 14 avr. 2016 à 21:07, Greg MacDonald <gmacdonald at trionworlds.com> a
> That’s concerning. I don’t have any tips I’m afraid. But I’ve noticed that
> after a build is requested it’s impossible to tell if it’s waiting on a
> worker to become available or if it’s actually been forgotten. But so far
> all my requests have eventually found their way to a worker after a few
> minutes. I’m only working with two at the moment though. It would be nice
> if the queues were made explicit in the UI.
> *From:* users [mailto:users-bounces at buildbot.net] *On Behalf Of *Ed
> *Sent:* Thursday, April 14, 2016 3:36 AM
> *To:* users at buildbot.net
> *Subject:* [users at bb.net] Triggered builds getting skipped
> Using buildbot 0.9.0b7 (I haven't had a chance to test it on b8 yet), I'm
> getting a problem where some triggered builds get skipped without doing
> It appears that buildrequests aren't creating builds. It also seems that
> if we keep the number of triggered builds down to about 6, it doesn't
> happen very often. If we increase them to 12 it reliably happens every
> time we kick off a parent build.
> I'm not really sure what to look at or how to investigate it, so any tips
> would be helpful.
> users mailing list
> users at buildbot.net
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the users