Closed Bug 1181793 Opened 5 years ago Closed 5 years ago
.json to point to http://hg .mozilla for esr38 -> m-c .org/build/mozharness/rev/4a31e6739409
we ran into a few hiccups today where we tried to bump mozharness.json across trees. the main motivation to do so prior to landing mozharness in every tree is to start at clean slate where mozharness is the same across trees. That way, when new patches land on m-c, they will merge/uplift without conflicts across release branches. In other words, if we don't do this, and instead put a copy of mozharness that matches each tree's current pin, we will have wildly different patches across trees and thus those patches + new patches that land on m-c won't apply when they merge.
landed the fix for the --chunk-by-runtime problems, along with a couple of other patches requested by RyanVM: https://treeherder.mozilla.org/#/jobs?repo=mozilla-esr38&revision=bc85fa00c9f7
And mozilla-release. https://hg.mozilla.org/releases/mozilla-release/rev/f09937d1e4f2
For a quick status update, Aurora should be good to go at this point. Beta, Release, and esr38 will need bug 917999 part 3 rebased onto them in order to fix cpptest bustage from the mozharness part of that bug. Beyond that, I'm unaware of anything else needing uplift at this point in order to support this work.
I just landed bug 917999 and the associated follow-up patches on Beta, if all goes well there I'll do the same for Release and esr38.
Also, mozharness.json is already pointing to rev 4a31e6739409 on trunk & aurora, which postdates rev 43f7600b8c80.
Status: NEW → RESOLVED
Closed: 5 years ago
Resolution: --- → FIXED
Summary: update mozharness.json to point to http://hg.mozilla.org/build/mozharness/rev/43f7600b8c80 for esr38 -> m-c → update mozharness.json to point to http://hg.mozilla.org/build/mozharness/rev/4a31e6739409 for esr38 -> m-c
You need to log in before you can comment on or make changes to this bug.