New issue
Advanced search Search tips

Issue 922575 link

Starred by 1 user
Status: WontFix
Owner:
afakhry@chromium.org
Closed: Today
Cc:
zamorzaev@chromium.org
akes...@chromium.org
slangley@chromium.org
semenzato@chromium.org
chromeos-continuous-integration-fire-hose@google.com
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 2
Type: Bug



Sign in to add a comment

betty-chrome-pfq failed due to timeout

Project Member Reported by afakhry@chromium.org, Jan 16 (6 days ago) 
- betty-chrome-pfq: https://cros-goldeneye.corp.google.com/chromeos/healthmonitoring/buildDetails?buildbucketId=8924180830984979072

cbuildbot failed:

It seems this run took too long that it timed out. BuildPackages for example took 2+ hours (37% longer than average according to the page). SyncChrome is 392% longer than average!


jclinton@ is this something you can take a look at? Thanks!

Comment 1 by jclinton@chromium.org, Jan 16 (6 days ago)

Labels: -Pri-1 Pri-2
Owner: afakhry@chromium.org
BuildPackages took so long because of the Chrome build. Chrome build and SyncChrome are Gardener territory since we don't know much about either of those.

Comment 2 by jclinton@chromium.org, Jan 16 (6 days ago)

Cc: zamorzaev@chromium.org
Components: Infra>ChromeOS>Test>Platform
Also worth noting that--even with all of that--this would have succeeded if the VMTests hadn't flaked/timed out. That's something that Alex is working on.

Comment 3 by afakhry@chromium.org, Today (13 hours ago)

Status: WontFix (was: Assigned)
betty-chrome-pfq is currently successful.
►

Sign in to add a comment