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.
tegra-065 has been disabled
back in production
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.
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.
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.
(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.
Bug 759101 filed to have it pulled from service.
I'm going to remove this slave from production_config.py.
No longer a buildduty concern. Thanks Armen!