Closed Bug 1392700 Opened 3 years ago Closed 3 years ago

Upgrade mozharness tests to Mercurial 4.3


(Release Engineering :: Applications: MozharnessCore, enhancement)

Not set


(firefox56 fixed, firefox57 fixed)

Tracking Status
firefox56 --- fixed
firefox57 --- fixed


(Reporter: gps, Assigned: gps)




(3 files)

mozharness is currently testing with Mercurial 4.1. We've updated to Mercurial 4.3.1 pretty much everywhere for security fixes. We should test with the Mercurial we actually use in CI.
Isn't that driven by PuppetAgain or any other provision tools for the VMs? I'm fairly sure that mozharness just uses what the operating system has installed. So bug 1390299 would cover OS X.

Greg, is that correct? If yes do we also have bugs filed for Windows and Linux workers?
Flags: needinfo?(garndt)
Mercurial is being mass upgraded. This is tracked in various bugs. See the "hg43" tracking bug.
Flags: needinfo?(garndt)
Comment on attachment 8899922 [details]
Bug 1392700 - Use Mercurial 4.3 in mozharness tests;
Attachment #8899922 - Flags: review?(aki) → review+
Comment on attachment 8899923 [details]
Bug 1392700 - Initialize repository using latest requirements;

I'm not sure why dotencode either, other than getting windows unit tests to pass. If they pass without it, I'm happy to have it gone.
Attachment #8899923 - Flags: review?(aki) → review+
Pushed by
Use Mercurial 4.3 in mozharness tests; r=aki
Initialize repository using latest requirements; r=aki
Vendor robustcheckout with capabilities detection; r=glob
Attachment #8899924 - Flags: review?(glob)
You need to log in before you can comment on or make changes to this bug.