Tests on toolchain nightly buildbots (amd64) fail due to "CrOS auto-update failed for host ..." |
||||||||
Issue descriptionThe amd64 toolchain buildbots for testing gcc/llvm are here: gcc: https://uberchromegw.corp.google.com/i/chromeos/builders/amd64-gcc-toolchain llvm: https://uberchromegw.corp.google.com/i/chromeos/builders/amd64-llvm-toolchain Tests on these buildbots fail frequently with either of "Unhandled DevServerException: CrOS auto-update failed for host aaa.bbb.ccc.ddd: has reached AU retry limit." or "Unhandled DevServerException: CrOS auto-update failed for host aaa-bbb-ccc-ddd: No JSON object could be decoded" For example, see these two runs from 10/12/2016: -) https://uberchromegw.corp.google.com/i/chromeos/builders/amd64-gcc-toolchain/builds/30 -) https://uberchromegw.corp.google.com/i/chromeos/builders/amd64-llvm-toolchain/builds/29 These errors are the primary cause these builders are red on most days.
,
Oct 13 2016
,
Oct 13 2016
,
Oct 13 2016
This seems to be related, in which falco-chrome-pfq fails frequently with the same reason. https://bugs.chromium.org/p/chromium/issues/detail?id=655330
,
Dec 26 2017
,
Jan 2 2018
[It appears that a bunch of old cros issues bulk-added the "Infra" component recently, but they should probably be "Infra>Client>ChromeOS".]
,
Mar 30 2018
,
Mar 30 2018
,
Jun 29 2018
I guessing this is no longer an issue since no one has pinged the bug since 2016. Please reopen if you're still seeing this. |
||||||||
►
Sign in to add a comment |
||||||||
Comment 1 by llozano@chromium.org
, Oct 13 2016Labels: -Build-Toolchain Build