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

Issue 884901 link

Starred by 1 user

Issue metadata

Status: Duplicate
Merged: issue 888108
Owner:
Closed: Sep 21
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 1
Type: Bug

Blocking:
issue 888108



Sign in to add a comment

veyron_minnie-tot-chrome-pfq-informational failing in HWTest on DUT chromeos2-row6-rack2-host3

Project Member Reported by steve...@chromium.org, Sep 17

Issue description

veyron_minnie-tot-chrome-pfq-informational is failing in HWTest [bvt-arc] with messages like:

host: chromeos2-row6-rack2-host3, status: Repair Failed, locked: False diagnosis: Failed repair

It isn't failing (in this suite) every run, and it always seems to be chromeos2-row6-rack2-host3, so the issue may be a problem with that DUT.

 
Seeing a similar failure in bvt-inline and bvt-cq with the same DUT: chromeos2-row6-rack2-host3

Cc: jkop@chromium.org
Summary: veyron_minnie-tot-chrome-pfq-informational failing in HWTest on DUT chromeos2-row6-rack2-host3 (was: veyron_minnie-tot-chrome-pfq-informational failing in HWTest [bvt-arc])
Components: -Infra>Client>Chrome Infra>Client>ChromeOS
Cc: bhthompson@google.com
Owner: akes...@chromium.org
Status: Assigned (was: Untriaged)
Per akeshet@, I locked the device at http://cautotest-prod/afe/#tab_id=view_host

Also added a YAQs entry:
https://yaqs.googleplex.com/eng/q/4684825135677440

Assigning to the Infra Deputy in case there is any follow up to be done after locking a DUT.

Blocking: 888108
Mergedinto: 888108
Status: Duplicate (was: Assigned)

Sign in to add a comment