Closed
Bug 876004
(t-w732-ix-003)
Opened 13 years ago
Closed 8 years ago
t-w732-ix-003 problem tracking
Categories
(Infrastructure & Operations Graveyard :: CIDuty, task, P3)
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: armenzg, Unassigned)
References
Details
(Whiteboard: [buildduty])
Loaned to Q.
| Reporter | ||
Updated•13 years ago
|
Blocks: t-w732-ix-004
Updated•13 years ago
|
No longer blocks: t-w732-ix-004
| Assignee | ||
Updated•13 years ago
|
Product: mozilla.org → Release Engineering
Updated•12 years ago
|
QA Contact: armenzg → bugspam.Callek
Comment 1•11 years ago
|
||
back in production
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
Comment 2•11 years ago
|
||
And burning jobs.
https://treeherder.mozilla.org/logviewer.html#?job_id=1589144&repo=mozilla-central
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
Comment 3•11 years ago
|
||
I'd bet that what he meant was "and burning jobs by running at the wrong resolution" since I think it's actually been months since we last got a Windows test slave back into production with working resolution.
Comment 4•11 years ago
|
||
Returned to production.
Status: REOPENED → RESOLVED
Closed: 11 years ago → 11 years ago
Resolution: --- → FIXED
Comment 6•11 years ago
|
||
I fixed up the CNAME in inventory.
Status: REOPENED → RESOLVED
Closed: 11 years ago → 11 years ago
Resolution: --- → FIXED
Comment 7•11 years ago
|
||
This still doesn't appear to be taking jobs.
Status: RESOLVED → REOPENED
Flags: needinfo?(coop)
Resolution: FIXED → ---
Comment 8•11 years ago
|
||
It's running a job right now.
Status: REOPENED → RESOLVED
Closed: 11 years ago → 11 years ago
Flags: needinfo?(coop)
Resolution: --- → FIXED
Comment 9•11 years ago
|
||
Burned the first job it took in a very suspicious-looking fashion. Re-disabled.
https://treeherder.mozilla.org/logviewer.html#?job_id=3750413&repo=fx-team
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
Comment 10•11 years ago
|
||
...lets see what a reimage will do.
Status: REOPENED → RESOLVED
Closed: 11 years ago → 11 years ago
Resolution: --- → FIXED
Comment 11•11 years ago
|
||
Running at the wrong resolution. Disabled again.
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
Comment 12•11 years ago
|
||
Re-enabled.
Status: REOPENED → RESOLVED
Closed: 11 years ago → 11 years ago
Resolution: --- → FIXED
Comment 13•11 years ago
|
||
(In reply to Ryan VanderMeulen [:RyanVM UTC-4] from comment #11)
> Running at the wrong resolution. Disabled again.
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
Comment 14•11 years ago
|
||
Guessing that final one was the confusion over the code regression that makes Win7 slaves running at their correct 1280x1024 hit the failure that only on Win8 means the resolution is wrong, reenabled.
Status: REOPENED → RESOLVED
Closed: 11 years ago → 11 years ago
Resolution: --- → FIXED
Comment 15•9 years ago
|
||
Attempting SSH reboot...Failed.
Attempting IPMI reboot...Failed.
Filed IT bug for reboot (bug 1309053)
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
Comment 16•9 years ago
|
||
Back online and taking jobs.
Status: REOPENED → RESOLVED
Closed: 11 years ago → 9 years ago
Resolution: --- → FIXED
Comment 17•8 years ago
|
||
Attempting SSH reboot...Failed.
Attempting IPMI reboot...Failed.
Machine is unreachable, manual intervention required
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
Comment 18•8 years ago
|
||
Back online.
Status: REOPENED → RESOLVED
Closed: 9 years ago → 8 years ago
Resolution: --- → FIXED
Updated•8 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
•