[Buildbot-commits] [Buildbot] #2512: waterfall re-using build IDs, causes strange behavior in logs from individual steps

Buildbot trac trac at buildbot.net
Mon Jun 24 03:07:52 UTC 2013


#2512: waterfall re-using build IDs, causes strange behavior in logs from
individual steps
--------------------+--------------------
Reporter:  RockHed  |       Owner:
    Type:  defect   |      Status:  new
Priority:  major    |   Milestone:  0.8.+
 Version:  0.8.7p1  |  Resolution:
Keywords:           |
--------------------+--------------------

Comment (by RockHed):

 It's not restarting "often" (the failures here were induced manually to
 test this), but it has a few times due to an unrelated issue.

 I put a try/except around the line in question (the sourcestamps.extend
 function), and it seems to have worked, with a small glitch -- the build
 isn't seen on the buildslave status page, only on the builder status page,
 with revision unknown.  Going into it to see the details gets an
 exception, because cxt['start'] is 'None'.  I can probably hack at this a
 bit more, but I've reached the main goal, which was to make sure the next
 run is incremented.  Thanks for the help.

-- 
Ticket URL: <http://trac.buildbot.net/ticket/2512#comment:10>
Buildbot <http://buildbot.net/>
Buildbot: build/test automation


More information about the Commits mailing list