Closed Bug 1270674 Opened 8 years ago Closed 7 years ago

Mercurial 3.7.3 not being used on Linux64 Valgrind builds

Categories

(Release Engineering :: General, defect)

Product:
Release Engineering
Component:
General
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED FIXED

People

(Reporter: gps, Unassigned)

References

Details

My try push at https://treeherder.mozilla.org/#/jobs?repo=try&revision=1d09ba11d2d6e6d742b84fd0279a392dba6024b8 and specifically the Linux64 Valgrind build job (http://archive.mozilla.org/pub/firefox/try-builds/gszorc@mozilla.com-1d09ba11d2d6/try-linux64/try-linux64-valgrind-bm78-try1-build5242.txt.gz) is using Mercurial 3.1.2. See https://treeherder.mozilla.org/logviewer.html#?job_id=20432788&repo=try#L2130 for the log lines.

Not sure if this is a PATH issue or what. I thought 3.7.3 was installed on all the builders.
It's probably using the system hg rather than the one in /tools or mock?

Very tempting to WONTFIX this in favour of porting these builds to use mozharness in TC (bug 1251297)
Bug 1274488 fixed the hg version. We're still using a stale bundle and hgtool, although bug 1270951 may help with that.
we're not using hgtool / buildbot for valgrind builds any more
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → FIXED
Component: General Automation → General
You need to log in before you can comment on or make changes to this bug.