#2028: startBuild failing with assertion, causes builder to never fire.
---------------------+------------------------
Reporter: bdbaddog | Owner:
Type: defect | Status: new
Priority: major | Milestone: undecided
Version: 0.8.4p1 | Resolution:
Keywords: |
---------------------+------------------------
Comment (by dustin):
That confirms what I thought - this assertion assumes that newBuild and
startBuild will be called back-to-back, and in this case that doesn't
happen. So removing the assertion is the correct fix.
--
Ticket URL: <http://trac.buildbot.net/ticket/2028#comment:2>
Buildbot <http://buildbot.net/>
Buildbot: build/test automation
------------------------------------------------------------------------------
All of the data generated in your IT infrastructure is seriously valuable.
Why? It contains a definitive record of application performance, security
threats, fraudulent activity, and more. Splunk takes this data and makes
sense of it. IT sense. And common sense.
http://p.sf.net/sfu/splunk-d2d-c2
_______________________________________________
Buildbot-commits mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/buildbot-commits
