Closed
Bug 1181793
Opened 9 years ago
Closed 9 years ago
update mozharness.json to point to http://hg.mozilla.org/build/mozharness/rev/4a31e6739409 for esr38 -> m-c
Categories
(Release Engineering :: Applications: MozharnessCore, defect)
Release Engineering
Applications: MozharnessCore
Tracking
(firefox39 fixed, firefox40 fixed, firefox41 fixed, firefox42 fixed, firefox-esr31 unaffected, firefox-esr38 fixed, b2g-v2.0 unaffected, b2g-v2.0M unaffected, b2g-v2.1 unaffected, b2g-v2.1S unaffected, b2g-v2.2 unaffected, b2g-master fixed)
RESOLVED
FIXED
| Tracking | Status | |
|---|---|---|
| firefox39 | --- | fixed |
| firefox40 | --- | fixed |
| firefox41 | --- | fixed |
| firefox42 | --- | fixed |
| firefox-esr31 | --- | unaffected |
| firefox-esr38 | --- | fixed |
| b2g-v2.0 | --- | unaffected |
| b2g-v2.0M | --- | unaffected |
| b2g-v2.1 | --- | unaffected |
| b2g-v2.1S | --- | unaffected |
| b2g-v2.2 | --- | unaffected |
| b2g-master | --- | fixed |
People
(Reporter: jlund, Assigned: jlund)
References
Details
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.
|
Assignee | |
Updated•9 years ago
|
|
||
Comment 1•9 years ago
|
||
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
|
||
Comment 2•9 years ago
|
||
And mozilla-release. https://hg.mozilla.org/releases/mozilla-release/rev/f09937d1e4f2
Assignee: nobody → jgriffin
status-firefox39:
--- → fixed
|
|
||
Comment 3•9 years ago
|
||
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.
Assignee: jgriffin → jlund
status-firefox39:
fixed → ---
|
||
Comment 4•9 years ago
|
||
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.
|
|
||
Comment 5•9 years ago
|
||
Also, mozharness.json is already pointing to rev 4a31e6739409 on trunk & aurora, which postdates rev 43f7600b8c80.
|
|
||
Updated•9 years ago
|
status-b2g-v2.0:
--- → unaffected
status-b2g-v2.0M:
--- → unaffected
status-b2g-v2.1:
--- → unaffected
status-b2g-v2.1S:
--- → unaffected
status-b2g-v2.2:
--- → unaffected
status-b2g-master:
--- → fixed
status-firefox39:
--- → affected
status-firefox40:
--- → affected
status-firefox41:
--- → fixed
status-firefox42:
--- → fixed
status-firefox-esr31:
--- → unaffected
status-firefox-esr38:
--- → affected
|
|
||
Comment 6•9 years ago
|
||
https://hg.mozilla.org/mozilla-central/rev/f34a7120f46b https://hg.mozilla.org/releases/mozilla-aurora/rev/b0a8e3986e35 https://hg.mozilla.org/releases/mozilla-beta/rev/65ee607d815f
|
|
Assignee | |
Updated•9 years ago
|
Status: NEW → RESOLVED
Closed: 9 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.
Description
•