#2551: Triggered builds containing steps synchronized by a SlaveLock (counting
or
exclusive) are sometimes not run.
---------------------+--------------------
Reporter: cmumford | Owner:
Type: defect | Status: new
Priority: major | Milestone: 0.8.+
Version: 0.8.7p1 | Resolution:
Keywords: locks |
---------------------+--------------------
Changes (by dustin):
* keywords: Triggerable => locks
* milestone: undecided => 0.8.+
Comment:
Do the builds *never* run? One possibility here is that the release of
the locks is not correctly initiating a check for runnable build requests.
But if that's the case, then eventually (I think at a 30-minute interval)
the builds would be run anyway. The 30-minute timer is a kind of backup
process for missed triggers like this.
Otherwise, something deeper is wrong :(
--
Ticket URL: <http://trac.buildbot.net/ticket/2551#comment:1>
Buildbot <http://buildbot.net/>
Buildbot: build/test automation
------------------------------------------------------------------------------
Introducing Performance Central, a new site from SourceForge and
AppDynamics. Performance Central is your source for news, insights,
analysis and resources for efficient Application Performance Management.
Visit us today!
http://pubads.g.doubleclick.net/gampad/clk?id=48897511&iu=/4140/ostg.clktrk
_______________________________________________
Buildbot-commits mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/buildbot-commits
