Closed
Bug 889274
(b-2008-ix-0067)
Opened 12 years ago
Closed 10 years ago
b-2008-ix-0067 problem tracking
Categories
(Infrastructure & Operations Graveyard :: CIDuty, task, P3)
Infrastructure & Operations Graveyard
CIDuty
x86_64
Windows Server 2008
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: Callek, Unassigned)
References
Details
(Whiteboard: [buildduty][buildslaves][capacity])
host is down, OOB not responding
Reporter | ||
Comment 1•12 years ago
|
||
happily taking jobs
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → FIXED
Assignee | ||
Updated•12 years ago
|
Product: mozilla.org → Release Engineering
Summary: w64-ix-slave08 problem tracking → b-2008-ix-0067 problem tracking
Comment 2•11 years ago
|
||
burned a make pkg test job with:
find: Filesystem loop detected; `dist/test-stage/xpcshell/tests/toolkit/devtools/pretty-fast/tests/unit' is part of the same filesystem loop as `dist/test-stage/xpcshell/tests/toolkit/devtools/pretty-fast/tests/unit'.
I disabled it once it started the same job again in case it would repeat and I'd need to clobber the builddir. it greened its next job so I am re-enabling
Comment 3•10 years ago
|
||
Attempting SSH reboot...Failed.
Attempting IPMI reboot...Failed.
Filed IT bug for reboot (bug 1139912)
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
Updated•10 years ago
|
Status: REOPENED → RESOLVED
Closed: 12 years ago → 10 years ago
Resolution: --- → FIXED
Comment 4•10 years ago
|
||
Died in the middle of a job yesterday, and despite claiming that it is rebooting, hasn't done anything (including connect to a master, after I did a disable-reboot-reboot-enable-reboot cycle) since.
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
Comment 5•10 years ago
|
||
Then it magically got better.
Status: REOPENED → RESOLVED
Closed: 10 years ago → 10 years ago
Resolution: --- → FIXED
Updated•7 years ago
|
Product: Release Engineering → Infrastructure & Operations
Updated•6 years ago
|
Product: Infrastructure & Operations → Infrastructure & Operations Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•