Closed
Bug 1614855
Opened 4 years ago
Closed 4 years ago
Perma valgrind-test | non-zero exit code from Valgrind: -139 due to the fact we use Ubuntu 18.04 in GCP
Categories
(Firefox Build System :: Task Configuration, defect)
Firefox Build System
Task Configuration
Tracking
(firefox-esr68 fixed, firefox73 fixed, firefox74 fixed, firefox75 fixed)
RESOLVED
FIXED
mozilla75
People
(Reporter: CosminS, Assigned: wcosta)
Details
Attachments
(1 file)
Failure log: https://treeherder.mozilla.org/logviewer.html#?job_id=288428655&repo=autoland
This is happening also on try: https://treeherder.mozilla.org/#/jobs?repo=try&resultStatus=busted%2Cexception&classifiedState=unclassified&revision=aa4c96e316731813a008ce636e9df2d34483e3f4&selectedJob=288451872
wcosta on slack: "I believe so, but it is not due to the cloud migration, but due to the fact we use Ubuntu 18.04 in GCP"
Flags: needinfo?(wcosta)
Flags: needinfo?(mozilla)
Assignee | ||
Comment 1•4 years ago
|
||
GCE instances use Ubuntu 18.04, which is known to cause issues in
valgrind builds (Bug 1545094), while EC2 uses Ubuntu 14.04.
Move valgrind builds back to GCE to avoid perma fail of these jobs.
Updated•4 years ago
|
Assignee: nobody → wcosta
Status: NEW → ASSIGNED
Assignee | ||
Comment 2•4 years ago
|
||
This patch moves valgrind builds back to EC2 as an emergency solution.
Flags: needinfo?(wcosta)
Pushed by malexandru@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/0ce5838679ee Run valgrind builds in AWS r=froydnj
Comment 4•4 years ago
|
||
bugherder uplift |
status-firefox74:
--- → fixed
Comment 5•4 years ago
|
||
bugherder uplift |
status-firefox-esr68:
--- → fixed
Comment 6•4 years ago
|
||
bugherder uplift |
status-firefox73:
--- → fixed
Comment 7•4 years ago
|
||
bugherder |
Status: ASSIGNED → RESOLVED
Closed: 4 years ago
status-firefox75:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → mozilla75
Comment hidden (Intermittent Failures Robot) |
Comment hidden (Intermittent Failures Robot) |
Updated•4 years ago
|
Flags: needinfo?(mozilla)
You need to log in
before you can comment on or make changes to this bug.
Description
•