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

Issue 687215 link

Starred by 2 users
Status: Duplicate
Merged: issue 686854
Owner:
akes...@chromium.org
Closed: Feb 2017
Cc:
█ leecy@chromium.org
█ uekawa@chromium.org
█ slavamn@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 2
Type: Bug



Sign in to add a comment

Many timeouts on canaries (signing state taking too long? )

Project Member Reported by semenzato@chromium.org, Jan 31 2017 
Many canaries timed out, but cannot pinpoint a common cause.

For instance:

celes-release/809 signing took 1h 45m (compared to 53m on a successful build)

ah but elm-release/811 signing took 40m, yet the build timed out too.  Here are the times of some stages:

BuildPackages 2:16
PaygenBuildDev 3:13

Comment 1 by semenzato@chromium.org, Jan 31 2017 

Some more info:

caroline-release/362:
BuildPackages 2:54
HWTest (bvt-inline) 2:25

Huh... the last time caroline-release succeeded was at buidl 328 on Jan 19.  :/  Guess we haven't noticed.  The build took 25,268 seconds.  BuildPackages took a similar time (3:03) but HWTest (bvt-inline) was only 1:03

https://viceroy.corp.google.com/chromeos/build_details?build_config=caroline-release&build_number=328&experimental=False&duration=1d&refresh=-1

Comment 2 by semenzato@chromium.org, Jan 31 2017 

asuka-release has failed the last 5 builds, all with timeouts.  The last one that succeeded lasted 6:42.

Maybe we're constantly too close to the edge.

Comment 3 by autumn@chromium.org, Jan 31 2017

Labels: -current-issue

Comment 4 by leecy@chromium.org, Feb 2 2017 

The afternoon canaries on 2/1 had what seemed like a big spate of timeouts as well.

Comment 5 by uekawa@chromium.org, Feb 2 2017 

seems like the last run had the timeout issue on many of the boards.

Comment 7 by akes...@chromium.org, Feb 6 2017

Mergedinto: 686854
Status: Duplicate (was: Untriaged)
►

Sign in to add a comment