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)
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.
Comment 1•11 years ago
|
||
back in production
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
Comment 2•10 years ago
|
||
Running at the wrong resolution.
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
Comment 3•10 years ago
|
||
Interestingly enough, this slave is now reenabled and in production, and has the slavealloc note "Windows 10 testing".
Comment 4•10 years ago
|
||
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.
Updated•10 years ago
|
QA Contact: armenzg → bugspam.Callek
Comment 5•10 years ago
|
||
But despite that, it merrily continued taking production jobs, so I've disabled it yet again.
Comment 6•10 years ago
|
||
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
Comment 7•8 years ago
|
||
The slave was re-imaged as a Windows 10 tester.
Status: REOPENED → RESOLVED
Closed: 11 years ago → 8 years ago
Resolution: --- → WONTFIX
Updated•7 years ago
|
Product: Release Engineering → Infrastructure & Operations
Updated•5 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
•