Closed Bug 873728 (t-w732-ix-044) Opened 11 years ago Closed 6 years ago

t-w732-ix-044 problem tracking

Categories

(Infrastructure & Operations Graveyard :: CIDuty, task, P3)

x86
Windows 7

Tracking

(Not tracked)

RESOLVED WONTFIX

People

(Reporter: philor, Unassigned)

References

Details

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

https://tbpl.mozilla.org/php/getParsedLog.php?id=23106002&tree=Fx-Team was a Pink Pixel of Death (actually two literally pink pixels) reftest failure. In just one test image, rather than the reference image we read over and over from memory, so it might have been two cosmic rays passing through the slave, but I'm going to start being suspicious of the RAM on this slave from now on.
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → INCOMPLETE
Why did you incomplete it? Is this so you can re-open if you see another issue on this specific machine?
Right, I'm not willing to say it's got bad RAM and we should disable it for a couple of weeks before running diagnostics (that always come back clean anyway) based on a single failure, but the existence of the bug will remind me of my suspicions when I'm puzzling over, say, an unfamiliar GC crash on the same slave.
And another PPoD in https://tbpl.mozilla.org/php/getParsedLog.php?id=23275374&tree=Mozilla-Inbound, RAM diagnostics time I'm afraid.
Status: RESOLVED → REOPENED
Resolution: INCOMPLETE → ---
Depends on: 890270
So this was sent for diags, but never taken out of production... its also taking green jobs, so I marked it as wontfix for diags, and we'll revisit if it hurts again
Status: NEW → RESOLVED
Closed: 11 years ago11 years ago
Resolution: --- → FIXED
Product: mozilla.org → Release Engineering
And that's 97 days sitting idle because the bug wasn't reopened to prompt diagnostics.
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
Depends on: 999225
Reenabled and rebooted, only a couple of weeks of sitting idle with a new graphics card.
Status: REOPENED → RESOLVED
Closed: 11 years ago10 years ago
QA Contact: armenzg → bugspam.Callek
Resolution: --- → FIXED
Lots of jobs ending up with "Connection to the other side was lost in a non-clean fashion". 
Disabled.
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
Did a re-image and returned it to prod.
Status: REOPENED → RESOLVED
Closed: 10 years ago7 years ago
Resolution: --- → FIXED
Attempting SSH reboot...Failed.
Filed IT bug for reboot (bug 1370555)
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
Back online
Status: REOPENED → RESOLVED
Closed: 7 years ago7 years ago
Resolution: --- → FIXED
Attempting SSH reboot...Failed.
Filed IT bug for reboot (bug 1373693)
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
Back online.
Status: REOPENED → RESOLVED
Closed: 7 years ago7 years ago
Resolution: --- → FIXED
Attempting SSH reboot...Failed.
Filed IT bug for reboot (bug 1375127)
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
Back online.
Status: REOPENED → RESOLVED
Closed: 7 years ago7 years ago
Resolution: --- → FIXED
Windows testing machine t-w732-ix-044 failing to work properly even after re-image.
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
Looks like there are a lot of "retry" status jobs.
Product: Release Engineering → Infrastructure & Operations
Checked on slave alloc and slave health > the machine seems to be disabled.
Status: REOPENED → RESOLVED
Closed: 7 years ago6 years ago
Resolution: --- → WONTFIX
Product: Infrastructure & Operations → Infrastructure & Operations Graveyard
You need to log in before you can comment on or make changes to this bug.