Closed
Bug 1125392
Opened 9 years ago
Closed 9 years ago
Fix mozharness tox setup
Categories
(Release Engineering :: Applications: MozharnessCore, defect)
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: armenzg, Assigned: armenzg)
Details
Attachments
(1 file)
|
884 bytes,
patch
|
rail
:
review+
|
Details | Diff | Splinter Review |
It always failed for me because I had a newer Mercurial.
Attachment #8553995 -
Flags: review?(rail)
|
||
Comment 1•9 years ago
|
||
Comment on attachment 8553995 [details] [diff] [review] add hg2.6 setup It looks to me. BTW, does the py27-hg3.2 target pass for you (it's not enabled by default)? It fails for me. I wonder if we should enable it, since most of the slaves have switched to mercurial 3.x
Attachment #8553995 -
Flags: review?(rail) → review+
|
Assignee | |
Comment 2•9 years ago
|
||
It does not pass. I was hoping to file a follow up bug to fix it. Should I still land it as-is?
|
|
||
Comment 3•9 years ago
|
||
(In reply to Armen Zambrano - Automation & Tools Engineer (:armenzg) from comment #2) > Should I still land it as-is? Yeah. It fixes the original issue.
|
|
Assignee | |
Comment 4•9 years ago
|
||
https://hg.mozilla.org/build/mozharness/rev/d4f6783185b6
|
||
Comment 5•9 years ago
|
||
a mozharness patch has from this bug is in production
|
|
Assignee | |
Updated•9 years ago
|
Assignee: nobody → armenzg
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•