New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 817269 link

Starred by 1 user

Issue metadata

Status: Fixed
Owner:
Closed: Feb 2018
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 2
Type: Bug



Sign in to add a comment

guado_moblab-paladin failed with "AutoservError: Moblab has 0 Ready DUTs"

Project Member Reported by nxia@chromium.org, Feb 28 2018

Issue description

https://luci-milo.appspot.com/buildbot/chromeos/guado_moblab-paladin/8762
https://luci-milo.appspot.com/buildbot/chromeos/guado_moblab-paladin/8763

guado_moblab-paladin keeps failing with "AutoservError: Moblab has 0 Ready DUTs"

There are 5 guado_moblab duts. around the build guado_moblab-paladin/8763, chromeos2-row1-rack8-host1 was locked by haddowk@, chromeos2-row1-rack8-host7 was running the moblab_runsuite, why the other duts were not "Ready" ?
 

Comment 1 by nxia@chromium.org, Feb 28 2018

Cc: haddowk@chromium.org
unlocked chromeos2-row1-rack8-host1 first, will do investigation tomorrow.
Cc: nxia@chromium.org
Owner: haddowk@chromium.org
Status: Assigned (was: Untriaged)
I can take the investigation
All the sub duts in stirling ct have been rebooted/recovered.

I have a task to get servo working on the moblab subduts which would be the long term solution.

Is there a way to have a custom repair / fail mechanism that would set this moblab to be "Repair Failed" there were other working devices in the lab but the test keeps trying the one with faulty subduts ?
Last CQ run was green.
Status: Fixed (was: Assigned)

Sign in to add a comment