Bug 876004 (t-w732-ix-003)

t-w732-ix-003 problem tracking

RESOLVED FIXED

Status

Infrastructure & Operations
CIDuty
P3
normal
RESOLVED FIXED
5 years ago
a month ago

People

(Reporter: armenzg, Unassigned)

Tracking

Details

(Whiteboard: [buildduty])

(Reporter)

Description

5 years ago
Loaned to Q.
(Reporter)

Updated

5 years ago
Blocks: 876005
(Reporter)

Updated

5 years ago
Depends on: 876013
No longer blocks: 876005
(Assignee)

Updated

5 years ago
Product: mozilla.org → Release Engineering
QA Contact: armenzg → bugspam.Callek

Comment 1

3 years ago
back in production
Status: NEW → RESOLVED
Last Resolved: 3 years ago
Resolution: --- → FIXED
And burning jobs.
https://treeherder.mozilla.org/logviewer.html#?job_id=1589144&repo=mozilla-central
Status: RESOLVED → REOPENED
Resolution: FIXED → ---

Updated

3 years ago
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.

Comment 4

3 years ago
Returned to production.
Status: REOPENED → RESOLVED
Last Resolved: 3 years ago3 years ago
Resolution: --- → FIXED

Comment 5

3 years ago
Hrmmm, still not in DNS.
Status: RESOLVED → REOPENED
Resolution: FIXED → ---

Comment 6

3 years ago
I fixed up the CNAME in inventory.
Status: REOPENED → RESOLVED
Last Resolved: 3 years ago3 years ago
Resolution: --- → FIXED
This still doesn't appear to be taking jobs.
Status: RESOLVED → REOPENED
Flags: needinfo?(coop)
Resolution: FIXED → ---

Comment 8

3 years ago
It's running a job right now.
Status: REOPENED → RESOLVED
Last Resolved: 3 years ago3 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
Last Resolved: 3 years ago3 years ago
Resolution: --- → FIXED
Running at the wrong resolution. Disabled again.
Status: RESOLVED → REOPENED
Resolution: FIXED → ---

Updated

3 years ago
Depends on: 1187051
Re-enabled.
Status: REOPENED → RESOLVED
Last Resolved: 3 years ago3 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
Last Resolved: 3 years ago3 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
Last Resolved: 3 years ago2 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
Last Resolved: 2 years ago7 months ago
Resolution: --- → FIXED

Updated

a month ago
Product: Release Engineering → Infrastructure & Operations
You need to log in before you can comment on or make changes to this bug.