New issue
Advanced search Search tips

Issue 905811 link

Starred by 1 user
Status: Assigned
Owner:
zamorzaev@chromium.org
Cc:
zamorzaev@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 1
Type: Bug



Sign in to add a comment

HWTest cheets_StartAndroid_P: ssh timed out

Project Member Reported by zwisler@google.com, Nov 15 
Failure on grunt-paladin:

https://cros-goldeneye.corp.google.com/chromeos/healthmonitoring/buildDetails?buildbucketId=8929774024678208816

relevant errors:

  cheets_StartAndroid_P.stress.0_SERVER_JOB            FAIL: ('ssh timed out', * Command:      /usr/bin/ssh -a -x  -o ControlPath=/tmp/_autotmp_X6vwzAssh-master/socket     -o Protocol=2 -o StrictHostKeyChecking=no -o UserKnownHostsFile=/dev/null     -o BatchMode=yes -o ConnectTimeout=30 -o ServerAliveInterval=900 -o     ServerAliveCountMax=3 -o ConnectionAttempts=4 -l root -p 22     chromeos2-row3-rack9-host13 "export LIBC_FATAL_STDERR_=1; if type     \"logger\" > /dev/null 2>&1; then logger -tag \"autotest\"     \"server[stack::get_kernel_ver|must_be_installed|run] -> ssh_run(ls     /bin/uname >/dev/null 2>&1)\";fi; ls /bin/uname >/dev/null 2>&1" Exit status: 255 Duration: 63.4518010616  stderr: ssh: connect to host chromeos2-row3-rack9-host13 port 22: Connection timed out)

Comment 1 by zamorzaev@chromium.org, Nov 15

Cc: zamorzaev@chromium.org
Labels: Hotlist-Deputy OS-Chrome
Owner: zwisler@chromium.org
The DUT (chromeos2-row3-rack9-host13) is OK after a repair was performed. I kicked off another reverify just in case.

Since this is a stress test, this is likely an honest test failure - the dut is overwhelmed with repeated requests. From the test description: "If this test is flaky every Android based test will be flaky as well."

This is worth investigating for a potential regression. I'm not sure who the right owner is, though.

Comment 2 by zamorzaev@chromium.org, Nov 15 

The dut reverification was successful.

Comment 3 by zwisler@google.com, Nov 15

Owner: bmgordon@chromium.org

Comment 4 by jclinton@chromium.org, Nov 15

Status: Assigned (was: Untriaged)

Comment 5 by bmgordon@chromium.org, Nov 15 

The error doesn't look like it has anything to do with the test itself.  It looks like ssh timed out when trying to set up the initial connection to the dut.

I see that the same dut failed with the same error on the dummy_Pass test twice already today.  Are we sure it isn't a hardware problem?

Comment 6 by jclinton@chromium.org, Nov 15

Owner: zamorzaev@chromium.org
Good point. Alex, we've had problems with USB network dongles in the past. Let's take this DUT out of rotation and have the HW lab team look at it.

Comment 7 by jclinton@chromium.org, Nov 15

Components: -Infra>Client>ChromeOS>CI Infra>Client>ChromeOS>Test

Comment 8 by pprabhu@chromium.org, Dec 3

Labels: -Hotlist-Deputy
Kick old bugs off deputy list
►

Sign in to add a comment