Closed
Bug 482649
Opened 15 years ago
Closed 15 years ago
Sendchange for hg relauto triggers branch builds
Categories
(Release Engineering :: General, defect, P2)
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: nthomas, Assigned: bhearsum)
References
Details
Attachments
(1 file)
521 bytes,
patch
|
catlee
:
review+
bhearsum
:
checked-in+
|
Details | Diff | Splinter Review |
The --branch=releases/mozilla-1.9.1 part of doing a sendchange to start the automation also triggers all the build/unit/leak builders (it matches their branch). We don't see this in staging because you have to use users/stage-ffxbld/mozilla-1.9.1 there to act on the dummy repo. IIRC we use the branch for the Mercurial() operation in ReleaseBuildFactory (via MercurialBuildFactory), which is shared with the dep builds. Perhaps isHgPollerTriggered (or an analogue for sendchange) can help here.
Assignee | ||
Comment 1•15 years ago
|
||
Nick, I'm having trouble reproducing this behaviour with a test Buildbot...are you sure there weren't changes being landed around the same time? (I hope not!). I'm going to try and dig up older logs in meantime...
Assignee | ||
Comment 2•15 years ago
|
||
I found the problem, patch incoming.
Assignee: nobody → bhearsum
Priority: -- → P2
Assignee | ||
Comment 3•15 years ago
|
||
Looks like MozScheduler passes fileIsImportant=None and properties={} down to Scheduler, instead of passing the arguments it was passed. This patch fixes that.
Attachment #366904 -
Flags: review?(catlee)
Updated•15 years ago
|
Attachment #366904 -
Flags: review?(catlee) → review+
Comment 4•15 years ago
|
||
Comment on attachment 366904 [details] [diff] [review] fix MozScheduler to pass along arguments properly doh, can't believe I wrote that code.
Assignee | ||
Comment 5•15 years ago
|
||
Comment on attachment 366904 [details] [diff] [review] fix MozScheduler to pass along arguments properly changeset: 214:efb85303e890
Attachment #366904 -
Flags: checked‑in+ checked‑in+
Assignee | ||
Comment 6•15 years ago
|
||
buildbot master has been reconfig'ed for this.
Status: NEW → RESOLVED
Closed: 15 years ago
Resolution: --- → FIXED
Updated•11 years ago
|
Product: mozilla.org → Release Engineering
You need to log in
before you can comment on or make changes to this bug.
Description
•