#2606: Trigger step consumes 2 build slots on slave
--------------------+------------------------
Reporter: otrempe | Owner:
Type: defect | Status: new
Priority: major | Milestone: undecided
Version: 0.8.8 | Resolution:
Keywords: |
--------------------+------------------------
Comment (by dustin):
I can't replicate this with the following
{{{
c['schedulers'] = []
c['schedulers'].append(triggerable.Triggerable(name="a",
builderNames=["b"]))
c['schedulers'].append(ForceScheduler(
name="force",
builderNames=["a"]))
fa = factory.BuildFactory()
fa.addStep(Trigger(schedulerNames=['a'], waitForFinish=True))
fb = factory.BuildFactory()
fb.addStep(ShellCommand(command="true"))
from buildbot.config import BuilderConfig
c['builders'] = [
BuilderConfig(
name = "a",
slavenames = "example-slave",
factory = fa,
),
BuilderConfig(
name = "b",
slavenames = "other-slave",
factory = fb,
) ]
}}}
The build runs successfully despite both slaves having `max_builds=1`.
Can you offer a reproduction recipe?
--
Ticket URL: <http://trac.buildbot.net/ticket/2606#comment:1>
Buildbot <http://buildbot.net/>
Buildbot: build/test automation
------------------------------------------------------------------------------
Rapidly troubleshoot problems before they affect your business. Most IT
organizations don't have a clear picture of how application performance
affects their revenue. With AppDynamics, you get 100% visibility into your
Java,.NET, & PHP application. Start your 15-day FREE TRIAL of AppDynamics Pro!
http://pubads.g.doubleclick.net/gampad/clk?id=84349831&iu=/4140/ostg.clktrk
_______________________________________________
Buildbot-commits mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/buildbot-commits
