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

Issue 655367 link

Starred by 1 user

Issue metadata

Status: Archived
Owner: ----
Closed: Jun 2018
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 2
Type: Bug



Sign in to add a comment

Tests on toolchain nightly buildbots (amd64) fail due to "CrOS auto-update failed for host ..."

Project Member Reported by rahulchaudhry@chromium.org, Oct 12 2016

Issue description

The 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.

 
Cc: rahulchaudhry@chromium.org cmt...@chromium.org manojgupta@chromium.org tingyuan@chromium.org yunlian@chromium.org
Labels: -Build-Toolchain Build

Comment 2 by laszio@chromium.org, Oct 13 2016

Cc: laszio@chromium.org
Cc: -tingyuan@chromium.org

Comment 4 by laszio@chromium.org, 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
Components: Infra

Comment 6 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".]
Components: Infra>Client>ChromeOS>CI
Components: -Infra>Client>ChromeOS
Status: Archived (was: Untriaged)
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