Closed
Bug 1141534
Opened 9 years ago
Closed 9 years ago
Mulet nightly builds have incorrect automation mozconfigs
Categories
(Release Engineering :: Applications: MozharnessCore, defect)
Release Engineering
Applications: MozharnessCore
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: mshal, Assigned: mshal)
References
Details
Attachments
(2 files)
2.45 KB,
patch
|
jlund
:
review+
mshal
:
checked-in+
|
Details | Diff | Splinter Review |
4.12 KB,
patch
|
bhearsum
:
review+
|
Details | Diff | Splinter Review |
In bug 1132123 we moved mulet builds over to mozharness. The mulet mozconfigs are based on the browser mozconfigs, which set MOZ_AUTOMATION_UPLOAD_SYMBOLS=1 and MOZ_AUTOMATION_UPDATE_PACKAGING=1 when IS_NIGHTLY=yes. However, we don't want to do uploadsymbols and update-packaging for mulet, and the nightly builds break when it tries to do so. We'll need to update the mulet mozconfigs to force these to zero, and the browser mozconfigs to default to 1 if not set.
Comment hidden (Legacy TBPL/Treeherder Robot) |
Comment hidden (Legacy TBPL/Treeherder Robot) |
Comment hidden (Legacy TBPL/Treeherder Robot) |
Comment hidden (Legacy TBPL/Treeherder Robot) |
Assignee | ||
Comment 6•9 years ago
|
||
We don't want to do balrog updates for mulet builds, so delete the 'update' action. I also got rid of the other commented-out actions.
Attachment #8575442 -
Flags: review?(jlund)
Assignee | ||
Comment 7•9 years ago
|
||
mozconfig updates to disable uploadsymbols and update-packaging for mulet builds.
Attachment #8575444 -
Flags: review?(bhearsum)
Updated•9 years ago
|
Attachment #8575444 -
Flags: review?(bhearsum) → review+
Assignee | ||
Comment 8•9 years ago
|
||
https://hg.mozilla.org/integration/mozilla-inbound/rev/062749867598
Comment 10•9 years ago
|
||
Is there something else that needs to be set still? That did get merged to mozilla-central, though it didn't get marked, but while http://ftp.mozilla.org/pub/mozilla.org/b2g/nightly/2015/03/2015-03-11-01-02-31-mozilla-central/mozilla-central-linux64-mulet-nightly-bm77-build1-build15.txt.gz says it used a mozconfig with MOZ_AUTOMATION_UPDATE_PACKAGING=0, it (and all the other Mulet nightlies) still failed while trying to submit its nonexistent update to Balrog.
Assignee | ||
Comment 11•9 years ago
|
||
Yeah, the second patch on this bug is for mozharness, which disables trying to send the updates to balrog since we don't need that for mulet. After that, mulet nightlies should be green according to my staging tests.
Comment 13•9 years ago
|
||
Comment on attachment 8575442 [details] [diff] [review] mulet-disable-updates Review of attachment 8575442 [details] [diff] [review]: ----------------------------------------------------------------- <stamp>
Attachment #8575442 -
Flags: review?(jlund) → review+
Assignee | ||
Comment 14•9 years ago
|
||
Comment on attachment 8575442 [details] [diff] [review] mulet-disable-updates https://hg.mozilla.org/build/mozharness/rev/a603f0c284a6
Attachment #8575442 -
Flags: checked-in+
After https://hg.mozilla.org/mozilla-central/rev/062749867598 landed mulet nightlies are still failing, just differently: https://treeherder.mozilla.org/logviewer.html#?job_id=1146542&repo=mozilla-central Will https://hg.mozilla.org/build/mozharness/rev/a603f0c284a6 fix it?
Assignee | ||
Comment 16•9 years ago
|
||
It should, yeah. I'm running that on try now, and if that looks good I'll push an update to inbound to use the latest mozharness.
Assignee | ||
Comment 17•9 years ago
|
||
m-c is now using the mozharness fix, so if the next set of mulet nightlies doesn't work, then something else is broken. Please ping me if that's the case!
Comment 18•9 years ago
|
||
mozharness production tag moved to: https://hg.mozilla.org/build/mozharness/rev/d35bfd399151
Assignee | ||
Comment 19•9 years ago
|
||
Mulet nightlies are green now, closing.
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → FIXED
Comment 20•6 years ago
|
||
Removing leave-open keyword from resolved bugs, per :sylvestre.
Keywords: leave-open
You need to log in
before you can comment on or make changes to this bug.
Description
•