909160 - (b-2008-ix-0151) b-2008-ix-0151 problem tracking

Status: RESOLVED FIXED

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

Description

[Phil Ringnalda (:philor)]

Added by bug 894398, but missing keys and thus burning everything it touches. Disabled in slavealloc.

Comment 1

[Hal Wine [:hwine] use NI!]

fixed, re-enabled, rebooted

Comment 2

[Release Engineering SlaveAPI Service]

Attempting SSH reboot...Failed.
Attempting IPMI reboot...Failed.
Filed IT bug for reboot (bug 969056)

Comment 3

[Ryan VanderMeulen [:RyanVM]]

Seems to have a penchant for randomly burning builds without giving much indication as to why.
http://ftp.mozilla.org/pub/mozilla.org/firefox/tinderbox-builds/mozilla-aurora-win64/1426518201/mozilla-aurora-win64-bm82-build1-build54.txt.gz

Comment 4

[Phil Ringnalda (:philor)]

There's an indication, as long as you remember that most Windows build failures will be "filesystem loop detected" and search for that first, whenever no excuse for a failure is offered to you.

Comment 5

[Chris Cooper [:coop] (he/him)]

Re-imaged and returned to production.

Comment 6

[Phil Ringnalda (:philor)]

Every job it has tried today has ended in a 4800 seconds without output hang. Disabled, needs diagnostics.

Comment 7

[Phil Ringnalda (:philor)]

Wups, don't think this blocks *or* depends on diagnostics for a t-w864-ix slave.

Comment 8

[Phil Ringnalda (:philor)]

Oh, that was a summary typo that got corrected the wrong way, and poor t-w864-ix-151 had no idea why it was suddenly having to go to the doctor, or why b-2008-ix-0151 was snickering about it. Filed bug 1174976 to make this slave go to the doctor, too.

Comment 9

[Phil Ringnalda (:philor)]

Reenabled on a day when everything is timing out after 4800 seconds without output, so maybe it can sneak back in without anyone noticing for a while that it is different.