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

Issue 780667 link

Starred by 1 user

Issue metadata

Status: Archived
Owner:
Closed: Dec 2017
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: ----
Type: ----



Sign in to add a comment

kefka-release:1637 failed

Project Member Reported by justincarlson@chromium.org, Nov 2 2017

Issue description

kefka-release:1637 failed

Builders failed on: 
- kefka-release: 
  https://luci-milo.appspot.com/buildbot/chromeos/kefka-release/1637

This build has been failing for several days.  I see a lot of ssh connection failures to lots of different boards failing, ex:

chromeos2-row4-rack8-host4
chromeos2-row8-rack4-host15
chromeos2-row4-rack8-host7

The specific failure shows up in the logs as:

@@@STEP_LINK@[Test-Logs]: autoupdate_EndToEndTest.paygen_au_dev_full: retry_count: 1, FAIL: Unhandled DevServerException: CrOS auto-update failed for host chromeos2-row8-rack4-host15: 0) SSHConnectionError: ssh: connect to host chromeos2-row8-rack4-host15 port 22: Connection timed out@http://cautotest-prod/tko/retrieve_logs.cgi?job=/results/153042258-chromeos-test/@@@

 
Cc: akes...@chromium.org
The log message is misleading, the real error

Unhandled DevServerException: CrOS auto-update failed for host chromeos2-row4-rack8-host9: 0) SSHConnectionError: ssh: connect to host chromeos2-row4-rack8-host9 port 22: Connection timed out

chromeos2-row4-rack8-host9 shows up a lot too.

The DUTs have a long and troubled past, by which I mean they have been thrashing between provision and repair for a long time.

It seems like the DUTs are continuously not reachable via SSH.
Cc: shuqianz@chromium.org
Owner: akes...@chromium.org
Status: Archived (was: Available)

Sign in to add a comment