895121 - (t-w732-ix-017) t-w732-ix-017 problem tracking

Status: RESOLVED FIXED

(Infrastructure & Operations Graveyard :: CIDuty, task)

Comment 1

[[e-mail] (:bhearsum)]

Re-enabled and rebooted in slavealloc. Now back in production after nearly 2 months of pointless idleness.

Comment 2

[Phil Ringnalda (:philor)]

Did we do something about resolution or graphics in the meantime, that didn't get done to this slave?

https://tbpl.mozilla.org/php/getParsedLog.php?id=27460416&tree=Mozilla-Inbound is a reftest run that failed 126 webgl tests that nothing else fails; https://tbpl.mozilla.org/php/getParsedLog.php?id=27461104&tree=Fx-Team is a mochitest run that failed because we expect hardware graphics acceleration to be enabled on Win7, but it wasn't; https://tbpl.mozilla.org/php/getParsedLog.php?id=27458087&tree=Mozilla-Aurora is a mochitest failing webgl tests in a way that has never been seen before except on one other broken slave (which, alas, had no satisfactory resolution, the not-a-dongle was fine, it passed diagnostics, by then the resolution was fine and it went back into service without any clue as to what happened).

Disabled in slavealloc.

Comment 3

[Phil Ringnalda (:philor)]

Since last anyone spoke here: mostly in bug 873566, driver issues, apache issues, one weird failure that looked like maybe something was in the way over the browser, then it has settled in to being fine except for a complete inability to run xperf jobs, like https://tbpl.mozilla.org/php/getParsedLog.php?id=27891271&tree=Mozilla-Central

Disabled in slavealloc.

Comment 4

[Armen [:armenzg]]

Attachment: Graphics setup screenshot

Comment 5

[Armen [:armenzg]]

From dep bug: "can you give it a whirl and reopen if issues persist? we can also try and reimage it again and see if the graphic issues come back."

Comment 6

[[e-mail] (:bhearsum)]

(In reply to Armen Zambrano [:armenzg] (Release Engineering) (EDT/UTC-4) from comment #5)
> From dep bug: "can you give it a whirl and reopen if issues persist? we can
> also try and reimage it again and see if the graphic issues come back."

I put this slave back in production.

Comment 7

[Armen [:armenzg]]

I had wanted to run it through staging since I was not confident that it would succeed.
That is the reason that I still had it assigned rather than unassigned.
Let's hope it doesn't come back.

Comment 8

[[e-mail] (:bhearsum)]

Oh, sorry. I didn't see the assignment, and didn't take from the comments that you were testing it out.

Comment 9

[Phil Ringnalda (:philor)]

Unable to run xperf, https://tbpl.mozilla.org/php/getParsedLog.php?id=28674484&tree=UX. Disabled in slavealloc.

Comment 10

[Armen [:armenzg]]

The machine has been able to run xperf jobs without any issues on staging.
It's also been able to run opt unit tests with no failures.

I'm letting it take other talos jobs.

Comment 11

[Armen [:armenzg]]

I'm putting the machine back into production.
I found no issues with it on staging.

Comment 12

[Phil Ringnalda (:philor)]

Doesn't seem to have actually made it to production - https://secure.pub.build.mozilla.org/builddata/reports/slave_health/slave.html?class=test&type=t-w732-ix&name=t-w732-ix-017 says that it's connected to pp-tests, and that it hasn't done a job since October 2nd.

Comment 13

[Armen [:armenzg]]

*sigh*

Fixed now.

Comment 14

[Phil Ringnalda (:philor)]

Needs a reimage according to bug 1104225, disabled in slavealloc.

Comment 15

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

Re-imaged and returned to production.