Bug 883549 (bld-lion-r5-016)

bld-lion-r5-016 problem tracking

RESOLVED FIXED

Status

Release Engineering
Buildduty
P3
normal
RESOLVED FIXED
5 years ago
a year ago

People

(Reporter: philor, Unassigned)

Tracking

Firefox Tracking Flags

(Not tracked)

Details

(Whiteboard: [buildduty][buildslaves][capacity])

(Reporter)

Description

5 years ago
Can't create directories in tmpdir, fails make check, needs reimage.

Updated

5 years ago
No longer blocks: 880003

Comment 1

5 years ago
Back in production.
Status: NEW → RESOLVED
Last Resolved: 5 years ago
Resolution: --- → FIXED
(Assignee)

Updated

5 years ago
Product: mozilla.org → Release Engineering
(Reporter)

Comment 2

4 years ago
mozinstall bustage, needs a reimage, disabled in slavealloc.
Status: RESOLVED → REOPENED
Resolution: FIXED → ---

Comment 3

4 years ago
Kicked off a re-image, and re-enabled.
Status: REOPENED → RESOLVED
Last Resolved: 5 years ago4 years ago
Resolution: --- → FIXED
(Reporter)

Comment 4

4 years ago
mozinstall bustage, needs a reimage, disabled in slavealloc
Status: RESOLVED → REOPENED
Resolution: FIXED → ---

Comment 5

4 years ago
Re-imaged and re-enabled.
Status: REOPENED → RESOLVED
Last Resolved: 4 years ago4 years ago
Resolution: --- → FIXED
(Reporter)

Updated

3 years ago
No longer blocks: 874642
To document, just issued a reimage on this one.

<philor> how about reimaging just https://secure.pub.build.mozilla.org/builddata/reports/slave_health/slave.html?class=try&type=bld-lion-r5&name=bld-lion-r5-016 which has 5 failures in a row and hasn't produced any output in its current job for half an hour now?
(Reporter)

Comment 7

3 years ago
Seems not to have gone well, it hasn't actually done anything post-reimage.
Status: RESOLVED → REOPENED
QA Contact: armenzg → bugspam.Callek
Resolution: FIXED → ---
(Reporter)

Comment 8

3 years ago
Disabled since there's no point in my constant reboots of it.
Drives replaced, reimaged, re-enabled.
Status: REOPENED → RESOLVED
Last Resolved: 4 years ago3 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.