[Buildbot] #2917: Dependent scheduler gets wrong sourcestamp if builds merged?

Buildbot trac trac at buildbot.net
Thu Sep 25 21:06:19 UTC 2014

#2917: Dependent scheduler gets wrong sourcestamp if builds merged?
Reporter:  dank       |      Owner:
    Type:  undecided  |     Status:  new
Priority:  minor      |  Milestone:  undecided
 Version:  0.7.12     |   Keywords:
 As I was considering using the Dependent scheduler, I ran across a problem
 caused one team to stop using it,

 It's an old bug, probably in 0.7.12, but since Dependent is outdated,
 maybe it hasn't changed.

 The writeup is pretty good; it says in part

 "8:16:46 Chromium Builder (dbg) finishes build 24647.  A build is created
 which merges the 2 pending requests (or the master calls maybeStartBuild
 which checks to see if the 2 requests can be merged and does so).  A new
 source stamp is now used for Chromium Builder (dbg) which starts build
 *The dependent scheduler is not updated.*

 8:49:44 XP Tests (dbg)(1) starts build 28227 based on the original source
 stamp created at 7:47:01.  This uses revision r59371, though the dependent
 scheduler was fired because Chromium Builder (dbg) finished build 24647
 (for revision r59373).  The extract build step tries to grab r59371,
 grabs the unnumbered .zip.  At this point, the console will give wrong

 The key is that the tester's source stamp is not actually corrupted or
 incorrectly changed anywhere, it's just not updated to reflect its
 dependency's source stamp."

Ticket URL: <http://trac.buildbot.net/ticket/2917>
Buildbot <http://buildbot.net/>
Buildbot: build/test automation

More information about the bugs mailing list