Closed Bug 908373 (t-w864-ix-102) Opened 12 years ago Closed 8 years ago

t-w864-ix-102 problem tracking

Categories

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

x86_64
Windows 8

Tracking

(Not tracked)

RESOLVED WONTFIX

People

(Reporter: armenzg, Unassigned)

References

Details

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

An ipmitool reboot this not do the trick. It might need DCOps intervention.
Depends on: 912206
back in production
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
Running at the wrong resolution.
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
Interestingly enough, this slave is now reenabled and in production, and has the slavealloc note "Windows 10 testing".
It certainly appears that it was a Win10 slave as of yesterday's test runs of production jobs; I set it to dev/pp in slavealloc in hopes that we will thus stop live testing Win10 long before we're actually ready to do so.
QA Contact: armenzg → bugspam.Callek
But despite that, it merrily continued taking production jobs, so I've disabled it yet again.
Marking a dep (for now) on Bug 1191481 which is throwing this windows-8 machine that is striving to be a useable windows 10 machine, at our windows 10 test pool.
Depends on: 1191481
Depends on: 1182635
The slave was re-imaged as a Windows 10 tester.
Status: REOPENED → RESOLVED
Closed: 11 years ago8 years ago
Resolution: --- → WONTFIX
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.