Closed Bug 1191922 Opened 10 years ago Closed 10 years ago

comm-esr38 mozmill tests will not run

Categories

(Release Engineering :: General, defect)

defect
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: Fallen, Assigned: Fallen)

References

Details

Attachments

(1 file)

This is fallout from bug 917999. After we merged in the needed m-esr38 changesets to generate the right files, we are bitten by the fact that comm-esr38 is not using mozharness to run the mozmill builds. There are two options, either we attempt to enable mozharness for comm-esr38, or I fix the buildbot code to download the right tests. This will most likely need to happen at http://mxr.mozilla.org/build/source/buildbotcustom/process/factory.py#4239 I'd prefer trying the mozharness route though. I'd like someone to approve this before I attempt to do it though.
Flags: needinfo?(mkmelin+mozilla)
Flags: needinfo?(Pidgeot18)
Depends on: 1054308
Sounds good to me. You know a lot more about this than I do, so I trust your judgement.
Flags: needinfo?(mkmelin+mozilla)
(In reply to Philipp Kewisch [:Fallen] from comment #0) > This is fallout from bug 917999. After we merged in the needed m-esr38 > changesets to generate the right files, we are bitten by the fact that > comm-esr38 is not using mozharness to run the mozmill builds. > > There are two options, either we attempt to enable mozharness for > comm-esr38, or I fix the buildbot code to download the right tests. This > will most likely need to happen at > http://mxr.mozilla.org/build/source/buildbotcustom/process/factory.py#4239 > > I'd prefer trying the mozharness route though. I'd like someone to approve > this before I attempt to do it though. I know I moved to make mozmill support mozharness on TB 38 precisely so that we could enable mozharness tests on esr38 if need be. There might need to be a test fixup (see bug 1152287), but otherwise I think everything should work.
Flags: needinfo?(Pidgeot18)
Attached patch Fix - v1Splinter Review
This should do it. I was tempted to just remove the whole block, but I think we should rather clean up all of esr31 separately.
Attachment #8648410 - Flags: review?(Pidgeot18)
Version: 39 → 38
Comment on attachment 8648410 [details] [diff] [review] Fix - v1 Review of attachment 8648410 [details] [diff] [review]: ----------------------------------------------------------------- I see no problem with this, but I strictly speaking don't have r+ authority over releng code...
Attachment #8648410 - Flags: review?(Pidgeot18) → review+
Comment on attachment 8648410 [details] [diff] [review] Fix - v1 Review of attachment 8648410 [details] [diff] [review]: ----------------------------------------------------------------- xtra review from a relenger, for sanity
Attachment #8648410 - Flags: review+
Component: Build Config → General Automation
Product: Thunderbird → Release Engineering
QA Contact: catlee
Version: 38 → unspecified
This is merged to production now, running a build to verify.
Status: ASSIGNED → RESOLVED
Closed: 10 years ago
Resolution: --- → FIXED
Component: General Automation → General
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: