732886 - (tegra-065) tegra-065 problem tracking

Status: RESOLVED FIXED

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

Description

[Phil Ringnalda (:philor)]

An unimpressive 54% failure rate over the last 100 jobs, but more like 35% of the last 500 so there might be hope for it yet.

Comment 1

[Mike Taylor [:bear]]

tegra-065 has been disabled

Comment 2

[[e-mail] (:bhearsum)]

back in production

Comment 3

[Phil Ringnalda (:philor)]

It's currently refusing connections, after having spent 23:49:52 on a robocheck job, but it refusing connections is probably for the best: it's failed 50% of its last 200 jobs, so my comment 0 hope for it somehow recovering and not being worthless was probably misplaced.

Comment 4

[[e-mail] (:bhearsum)]

Bear, this tegra is now reimaged. I think you said it was moving to the staging pool or something...I can't find it on http://mobile-dashboard1.build.mtv1.mozilla.com/tegras/ anymore, so I bet you or Callek are doing something with it.

Comment 5

[Justin Wood (:Callek)]

This is "unassigned" (as in, no foopy is using it right now), but it just went down again yesterday so this reimage does not *seem* to have held, I just marked it for PDU reboot though, I'll get it tossed over the wall to clint if it stays bad, later staging if it comes back up.

Comment 6

[Justin Wood (:Callek)]

(In reply to Justin Wood (:Callek) from comment #5)
> I'll get it tossed over the wall to clint if it stays bad, later staging if it comes back up.

Bad again, "tegra agent check: connection refused"

TODO get it pulled for clint.

Comment 7

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

Bug 759101 filed to have it pulled from service.

Comment 8

[Armen [:armenzg]]

I'm going to remove this slave from production_config.py.

Comment 9

[[e-mail] (:bhearsum)]

No longer a buildduty concern. Thanks Armen!