several jobs fail on taskcluster-worker in resource leak test

RESOLVED FIXED in mozilla54

Status

P1
normal
RESOLVED FIXED
2 years ago
2 years ago

People

(Reporter: wcosta, Assigned: wcosta)

Tracking

unspecified
mozilla54
x86_64
Mac OS X

Details

User Story

mochitest-e10s, bc3,bc5,bc6,bc7
bc2 non-e10s
and mochitest-2 non-e10s

Attachments

(2 attachments)

(Assignee)

Updated

2 years ago
User Story: (updated)
Summary: mochitests-browser-chrome-2 fails on taskcluster-worker → several jobs fail on taskcluster-worker in resource leak test
(Assignee)

Updated

2 years ago
Duplicate of this bug: 1339037
(Assignee)

Updated

2 years ago
User Story: (updated)
(Assignee)

Updated

2 years ago
Assignee: nobody → wcosta
Status: NEW → ASSIGNED
(Assignee)

Comment 2

2 years ago
Created attachment 8840151 [details] [diff] [review]
Use system TMPDIR path. r=dustin

Some tests fail if we don't use the host TMPDIR path.
(Assignee)

Updated

2 years ago
Attachment #8840151 - Flags: review?(dustin)
(Assignee)

Comment 3

2 years ago
Created attachment 8840156 [details] [diff] [review]
Replicate BB environment variables. r=dustin

There are some environment variables necessary to run test jobs in BB
which are also necessary for taskcluster-worker. They were copied from
[1].

Additionally, native-engine was broken by bug 1325701. We fix it in this
commit.

[1] https://github.com/mozilla-releng/build-buildbotcustom/blob/master/env.py#L89-L96
(Assignee)

Updated

2 years ago
Attachment #8840156 - Flags: review?(dustin)
Attachment #8840151 - Flags: review?(dustin) → review+
Attachment #8840156 - Flags: review?(dustin) → review+

Comment 5

2 years ago
Pushed by ryanvm@gmail.com:
https://hg.mozilla.org/integration/mozilla-inbound/rev/f608a5a5d8e2
Replicate BB environment variables. r=dustin
Keywords: checkin-needed

Comment 6

2 years ago
bugherder
https://hg.mozilla.org/mozilla-central/rev/f608a5a5d8e2
Status: ASSIGNED → RESOLVED
Last Resolved: 2 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla54
You need to log in before you can comment on or make changes to this bug.