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

Issue 601813 link

Starred by 2 users

Issue metadata

Status: Duplicate
Merged: issue 809588
Owner:
Last visit > 30 days ago
Closed: May 2018
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 2
Type: ----



Sign in to add a comment

mixed-wificell-pre-cq consecutively fails due to suite timeout.

Project Member Reported by xixuan@chromium.org, Apr 8 2016

Issue description

https://uberchromegw.corp.google.com/i/chromiumos.tryserver/builders/wificell-pre-cq?numbuilds=200

Last 5 fail reasons:
build 89: crbugs/601511
build 88: suite job timeout, aborted
build 87: connection refused to host
build 86: suite job timeout, aborted
build 85: suite job timeout, aborted
 
Owner: tienchang@chromium.org
Status: Assigned (was: Untriaged)
Tien could you examine this and weigh in on whether this is still expected to work?
Hmm the wificell-pre-cq was successfully used (and passed) just last week. The devices are up and pingable. I'm not sure why there are so many of these failures. Actually, how can I tell what is invoking these trybot runs?
Components: Infra

Comment 4 by mmoss@chromium.org, Jan 2 2018

Components: -Infra Infra>Client>ChromeOS
[It appears that a bunch of old cros issues bulk-added the "Infra" component recently, but they should probably be "Infra>Client>ChromeOS".]
Cc: harpreet@chromium.org
Mergedinto: 809588
Status: Duplicate (was: Assigned)
It's a toss-up whether this should be Archived or Duplicate -- I'll go with Duplicate, since there's some more recent info on bug 809588 about this sort of thing still happening. I'm pretty sure this pre-cq is really likely to hit timeouts, given how many (sequential) builds it's running.

Sign in to add a comment