[Buildbot] #2813: Forced build never completes
Buildbot trac
trac at buildbot.net
Tue May 27 01:05:19 UTC 2014
#2813: Forced build never completes
--------------------+-----------------------
Reporter: sndgeek | Owner:
Type: defect | Status: new
Priority: major | Milestone: undecided
Version: 0.8.8 | Keywords:
--------------------+-----------------------
It appears that a forced build will never complete _if_ a build is forced
on a build slave with max_builds=1 and that slave is already running a
build. In the most recent case where I finally realized what might be
happening, I was forcing a run of another build that runs on the same
slave.
The build master appears to actually trigger the secondary build (which it
shouldn't do because max_builds=1) but then ignores all output from that
slave. The slave finishes but the master ignores its results and,
eventually, *all* builds will stall once that slave is scheduled for
another build. I can't guarantee that the next scheduled build is what
triggers this state but the master will definitely get locked up at some
point.
Once the system is in this state, the only way to fix it is to stop and
restart the master.
--
Ticket URL: <http://trac.buildbot.net/ticket/2813>
Buildbot <http://buildbot.net/>
Buildbot: build/test automation
More information about the bugs
mailing list