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.
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.
Attempting SSH reboot...Failed. Filed IT bug for reboot (bug 1012932)