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)

x86
Windows 7

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: armenzg, Unassigned)

References

Details

(Whiteboard: [buildduty])

Loaned to Q.
Depends on: 876013
No longer blocks: t-w732-ix-004
Product: mozilla.org → Release Engineering
QA Contact: armenzg → bugspam.Callek
back in production
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
Depends on: 1178010
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.
Returned to production.
Status: REOPENED → RESOLVED
Closed: 11 years ago11 years ago
Resolution: --- → FIXED
Hrmmm, still not in DNS.
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
I fixed up the CNAME in inventory.
Status: REOPENED → RESOLVED
Closed: 11 years ago11 years ago
Resolution: --- → FIXED
This still doesn't appear to be taking jobs.
Status: RESOLVED → REOPENED
Flags: needinfo?(coop)
Resolution: FIXED → ---
It's running a job right now.
Status: REOPENED → RESOLVED
Closed: 11 years ago11 years ago
Flags: needinfo?(coop)
Resolution: --- → FIXED
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 → ---
...lets see what a reimage will do.
Status: REOPENED → RESOLVED
Closed: 11 years ago11 years ago
Resolution: --- → FIXED
Running at the wrong resolution. Disabled again.
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
Depends on: 1187051
Re-enabled.
Status: REOPENED → RESOLVED
Closed: 11 years ago11 years ago
Resolution: --- → FIXED
(In reply to Ryan VanderMeulen [:RyanVM UTC-4] from comment #11) > Running at the wrong resolution. Disabled again.
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
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 ago11 years ago
Resolution: --- → FIXED
Attempting SSH reboot...Failed. Attempting IPMI reboot...Failed. Filed IT bug for reboot (bug 1309053)
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
Back online and taking jobs.
Status: REOPENED → RESOLVED
Closed: 11 years ago9 years ago
Resolution: --- → FIXED
Attempting SSH reboot...Failed. Attempting IPMI reboot...Failed. Machine is unreachable, manual intervention required
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
Back online.
Status: REOPENED → RESOLVED
Closed: 9 years ago8 years ago
Resolution: --- → FIXED
Product: Release Engineering → Infrastructure & Operations
Product: Infrastructure & Operations → Infrastructure & Operations Graveyard
You need to log in before you can comment on or make changes to this bug.