Closed Bug 878371 (t-xp32-ix-056) Opened 11 years ago Closed 10 years ago

t-xp32-ix-056 problem tracking

Categories

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

Product:
Infrastructure & Operations Graveyard
Component:
CIDuty
Platform:
x86
Windows XP
Type:
task

Tracking

(Not tracked)

Status:
RESOLVED FIXED

People

(Reporter: philor, Unassigned)

References

Details

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

https://tbpl.mozilla.org/php/getParsedLog.php?id=23655610&tree=Mozilla-Central&full=1 is the log from a test run this slave did at a time that it claimed was 17:05, but was actually 16:05.

Then the thought of this running a test with the clock an hour ahead got me worrying about how we might be setting the clock on all the new slaves - are we not setting it on boot when it's safe to do so, and also, are we letting Windows set it when it feels like doing so, so that at random times time will suddenly run backward? There are some new-slave-specific failures where that might make them suddenly make sense.
Depends on: 878391
Would you like me to disable this machine?

I will investigate the issue.
The machine got a GPO change to fix the timezone. It has been taking jobs in production.
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
Product: mozilla.org → Release Engineering
Attempting SSH reboot...Failed.
Filed IT bug for reboot (bug 1012932)
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
Status: REOPENED → RESOLVED
Closed: 11 years ago → 10 years ago
QA Contact: armenzg → bugspam.Callek
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.