Issue metadata
Sign in to add a comment
|
Lots of bot_update failures all of the sudden |
||||||||||||||||||||||||
Issue descriptionhttps://uberchromegw.corp.google.com/i/chromium.webkit/builders/WebKit%20Linux%20Precise%20Leak/builds/1692 https://uberchromegw.corp.google.com/i/chromium.win/builders/Win%20Builder%20%28dbg%29/builds/28957 https://uberchromegw.corp.google.com/i/chromium/builders/Win/builds/49043 I'm not yet sure what's up, investigating...
,
Nov 12 2016
These appear to be timeouts in the bot_update step: duration: 46 mins, 22 secs status: FAILURE status reason: return code was -1.
,
Nov 12 2016
Further investigation with bot whisperer martiniss showed that this is likely a network-related timeout when downloading/syncing boringssl over git. Semi-well known bug it seems.
,
Nov 12 2016
,
Nov 18 2016
+katthomas since you're on infra failure hunt. Added a couple of specific components, not sure which one suits better - please triage further. This might be related to the recent git fetch timeouts, see issue 663052.
,
Nov 21 2016
Persistent link: https://luci-milo.appspot.com/buildbot/chromium.webkit/WebKit%20Linux%20Precise%20Leak/1692 |
|||||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||||
Comment 1 by pdr@chromium.org
, Nov 12 2016