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

Issue 900488 link

Starred by 1 user

Issue metadata

Status: Assigned
Owner:
OOO
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 3
Type: Bug



Sign in to add a comment

dru duts failed repair

Project Member Reported by uekawa@google.com, Oct 31

Issue description

For scarlet/dru 
out of 10 pool:suites devices, 8 are Status "repair:Failed"

They need to be looked into?
 
Components: -Infra>Client>ChromeOS Infra>Client>ChromeOS>Test
Labels: OS-Chrome
Labels: Hotlist-Deputy
Owner: gu...@chromium.org
Querying via cautotest/ as of today.

Host				Status		Locked
chromeos6-row2-rack6-host1	Provisioning	No
chromeos6-row2-rack6-host4	Repair Failed	No
chromeos6-row6-rack12-host10	Repair Failed	Yes	DUT failed, ordered replacement
chromeos6-row6-rack12-host15	Repair Failed	No
chromeos6-row6-rack12-host19	Repair Failed	No
chromeos6-row6-rack12-host5	Ready		Yes	TEST
chromeos6-row6-rack12-host6	Repair Failed	No
chromeos6-row6-rack12-host7	Repair Failed	No	
chromeos6-row6-rack8-host12	Repair Failed	No	
chromeos6-row6-rack8-host2	Repair Failed	No


Is this something infra deputy can take a look at?
Status: Assigned (was: Untriaged)
This issue has an owner, a component and a priority, but is still listed as untriaged or unconfirmed. By definition, this bug is triaged. Changing status to "assigned". Please reach out to me if you disagree with how I've done this.

Sign in to add a comment