SkyLabHWTest failures on reef-chrome-pfq due unhealthy bot fleet. |
||||||||
Issue descriptionreef-chrome-pfq: https://cros-goldeneye.corp.google.com/chromeos/healthmonitoring/buildDetails?buildbucketId=8936278791177153600 Ton of failing tests.
,
Sep 5
,
Sep 5
Oh oops. Been buried in deputy stuff. Is there a way to mark a chrome pfq "experimental"?
,
Sep 5
,
Sep 5
This should be fixed, now that issue 878497 is fixed. The bvt pool looks good right now: http://shortn/_dLkHArgQ2P --> close_wait
,
Sep 6
Saw a successful run yesterday: https://cros-goldeneye.corp.google.com/chromeos/healthmonitoring/buildDetails?buildbucketId=8936248764940936240 Failures today are unrelated (BuildPackages) close_wait --> close
,
Sep 11
,
Sep 11
I just saw this happen again today. Bot: https://cros-goldeneye.corp.google.com/chromeos/healthmonitoring/buildDetails?buildbucketId=8935723023429833648 Log: https://luci-logdog.appspot.com/v/?s=chromeos/buildbucket/cr-buildbucket.appspot.com/8935723023429833648/+/steps/SkylabHWTest__bvt-arc_/0/stdout Let me know if you want me to file a separate issue.
,
Sep 11
,
Sep 11
Updating summary so that unrelated issues won't get deduped to this |
||||||||
►
Sign in to add a comment |
||||||||
Comment 1 by achuith@chromium.org
, Sep 5Components: 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)