[Buildbot-commits] [Buildbot] #2177: Trigger goes out to lunch and never comes back!
Buildbot
nobody at buildbot.net
Sun Jan 22 18:22:02 UTC 2012
#2177: Trigger goes out to lunch and never comes back!
--------------------------+------------------------
Reporter: seb_kuzminsky | Owner:
Type: undecided | Status: new
Priority: major | Milestone: undecided
Version: 0.8.5 | Resolution:
Keywords: |
--------------------------+------------------------
Comment (by dustin):
I'm trying to reproduce with a master.cfg containing:
{{{
NUM_BLDRS = 10
c['schedulers'] = []
c['schedulers'].append(triggerable.Triggerable(name="t",
builderNames=["sometask"]))
for x in range(NUM_BLDRS):
c['schedulers'].append(triggerable.Triggerable(name=str(x),
builderNames=["sometask"]))
c['schedulers'].append(timed.Periodic(name="n", periodicBuildTimer=1,
builderNames=["trig"]))
f1 = factory.BuildFactory()
f1.addStep(ShellCommand(command="echo hi", description='echoing',
descriptionDone='echoed', usePTY=True))
f2 = factory.BuildFactory()
f2.addStep(Trigger(schedulerNames=[ 't' ], waitForFinish=True))
f2.addStep(Trigger(schedulerNames=[ str(x) for x in range(NUM_BLDRS) ],
waitForFinish=True))
from buildbot.config import BuilderConfig
c['builders'] = [
BuilderConfig(
name = "sometask",
slavenames = "example-slave",
factory = f1,
category = 'x7',
mergeRequests = False
),
BuilderConfig(
name = "trig",
slavenames = "example-slave",
factory = f2,
category = 'x7',
mergeRequests = False
),
]
}}}
with the idea that when this fails, the "trig" builder will start to pile
up jobs waiting for the single slave builder it runs on.
700 builds in, I've still not seen a failure.
--
Ticket URL: <http://trac.buildbot.net/ticket/2177#comment:1>
Buildbot <http://buildbot.net/>
Buildbot: build/test automation
More information about the Commits
mailing list