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

Issue 880663 link

Starred by 1 user

Issue metadata

Status: Verified
Owner:
Closed: Sep 11
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 1
Type: Bug



Sign in to add a comment

SkyLabHWTest failures on reef-chrome-pfq due unhealthy bot fleet.

Project Member Reported by achuith@chromium.org, Sep 5

Issue description

Cc: djacobo@google.com
Components: Infra>Client>ChromeOS>CI
Owner: pprabhu@chromium.org
Summary: SkyLabHWTest failures on reef-chrome-pfq due to NO_RESOURCE (was: SkyLabHWTest failure on reef-chrome-pfq)
Another failure today:
https://cros-goldeneye.corp.google.com/chromeos/healthmonitoring/buildDetails?buildbucketId=8936223130662120576

Seems like an infra issue?


Components: -Infra>Client>ChromeOS>CI Infra>Client>ChromeOS>Test
Mergedinto: 878419
Status: Duplicate (was: Untriaged)
Oh oops.
Been buried in deputy stuff. 

Is there a way to mark a chrome pfq "experimental"?
Labels: Hotlist-Deputy
Status: Assigned (was: Duplicate)
Status: Started (was: Assigned)
This should be fixed, now that  issue 878497  is fixed. The bvt pool looks good right now: http://shortn/_dLkHArgQ2P

--> close_wait
Status: Fixed (was: Started)
Saw a successful run yesterday: https://cros-goldeneye.corp.google.com/chromeos/healthmonitoring/buildDetails?buildbucketId=8936248764940936240

Failures today are unrelated (BuildPackages)

close_wait --> close
Status: Assigned (was: Fixed)
Status: Verified (was: Assigned)
Re #7/#8: Not the same issue. Filed  issue 883066  to track this.
Summary: SkyLabHWTest failures on reef-chrome-pfq due unhealthy bot fleet. (was: SkyLabHWTest failures on reef-chrome-pfq due to NO_RESOURCE)
Updating summary so that unrelated issues won't get deduped to this

Sign in to add a comment