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

Issue 755247 link

Starred by 1 user
Status: Archived
Owner:
█ nxia@chromium.org
Last visit > 30 days ago
Closed: Nov 2017
Cc:
█ nxia@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 2
Type: Bug



Sign in to add a comment

HWTest failure: suite_jobs were aborted

Project Member Reported by nxia@chromium.org, Aug 14 2017 
https://luci-milo.appspot.com/buildbot/chromeos/reef-paladin/3292

suite was aborted. 

08/14 00:30:21.309 INFO |        server_job:0214| 	FAIL	134957170-chromeos-test/chromeos2-row7-rack6-host5/provision_AutoUpdate	provision	timestamp=1502695682	localtime=Aug 14 00:28:02	Unhandled DevServerException: CrOS auto-update failed for host chromeos2-row7-rack6-host5: SSHConnectionError: ssh: connect to host chromeos2-row7-rack6-host5 port 22: Connection timed out


08/14 00:33:57.207 INFO |        server_job:0214| 	FAIL	134957175-chromeos-test/chromeos2-row7-rack6-host11/provision_AutoUpdate.double	provision_AutoUpdate.double	timestamp=1502695901	localtime=Aug 14 00:31:41	Unhandled DevServerException: CrOS auto-update failed for host chromeos2-row7-rack6-host11: SSHConnectionError: ssh: connect to host chromeos2-row7-rack6-host11 port 22: Connection timed out


08/14 00:38:19.245 INFO |        server_job:0214| 	FAIL	134957167-chromeos-test/chromeos2-row7-rack6-host17/provision_AutoUpdate	provision	timestamp=1502695929	localtime=Aug 14 00:32:09	Unhandled DevServerException: CrOS auto-update failed for host chromeos2-row7-rack6-host17: SSHConnectionError: ssh: connect to host chromeos2-row7-rack6-host17 port 22: Connection timed out

Comment 1 by nxia@chromium.org, Aug 14 2017 

Looks like connections related to dev_server 100.115.245.197

https://pantheon.corp.google.com/storage/browser/chromeos-autotest-results/134957170-chromeos-test/chromeos2-row7-rack6-host5/debug

08/14 00:16:15.334 DEBUG|             utils:0212| Running 'ssh 100.115.245.197 'curl "http://100.115.245.197:8082/kill_au_proc?pid=8576&host_name=chromeos2-row7-rack6-host5"''

https://pantheon.corp.google.com/storage/browser/chromeos-autotest-results/134957167-chromeos-test/chromeos2-row7-rack6-host17/debug

08/14 00:18:07.399 DEBUG|             utils:0212| Running 'ssh 100.115.245.197 'curl "http://100.115.245.197:8082/kill_au_proc?pid=27817&host_name=100.115.230.64"''

Comment 2 Deleted

Comment 3 Deleted

Comment 4 by nxia@chromium.org, Aug 14 2017 

https://luci-milo.appspot.com/buildbot/chromeos/reef-paladin/3284

http://cautotest/tko/retrieve_logs.cgi?job=/results/134734147-chromeos-test/


also failed at SSHConnectionError
08/12 22:18:32.161 DEBUG|             utils:0212| Running 'ssh 100.115.245.200 'curl "http://100.115.245.200:8082/kill_au_proc?pid=13798&host_name=100.115.230.64"''
08/12 22:18:33.345 DEBUG|        dev_server:2153| Exception raised on auto_update attempt #2:
 Traceback (most recent call last):
  File "/home/chromeos-test/chromiumos/src/platform/dev/cros_update.py", line 216, in TriggerAU
    clobber_stateful=self.clobber_stateful)
  File "/home/chromeos-test/chromiumos/chromite/lib/auto_updater.py", line 979, in __init__
    payload_filename=payload_filename)
  File "/home/chromeos-test/chromiumos/chromite/lib/auto_updater.py", line 236, in __init__
    self.device_dev_dir = os.path.join(self.device.work_dir, 'src')
  File "/home/chromeos-test/chromiumos/chromite/lib/remote_access.py", line 657, in work_dir
    capture_output=True).output.strip()
  File "/home/chromeos-test/chromiumos/chromite/lib/remote_access.py", line 889, in BaseRunCommand
    return self.GetAgent().RemoteSh(cmd, **kwargs)
  File "/home/chromeos-test/chromiumos/chromite/lib/remote_access.py", line 344, in RemoteSh
    raise SSHConnectionError(e.result.error)
SSHConnectionError: ssh: connect to host 100.115.230.64 port 22: Connection timed out

Comment 5 by nxia@chromium.org, Aug 14 2017

Components: Infra>Client>ChromeOS
Labels: -OS-Android OS-Chrome

Comment 6 by nxia@chromium.org, Aug 14 2017

Summary: HWTest failure: suite_jobs were aborted (was: Auto-update failed at sshing to DUTs) (was: HWTest failure: suite_jobs were aborted)

Comment 7 by pprabhu@chromium.org, Aug 15 2017

Summary: HWTest failure: suite_jobs were aborted (was: HWTest failure: suite_jobs were aborted (was: Auto-update failed at sshing to DUTs))

Comment 8 by pprabhu@chromium.org, Aug 15 2017

Owner: nxia@chromium.org
Status: Assigned (was: Untriaged)
Looks like an incidence tracking bug for the deputy, so assigning as such.

Comment 10 by nxia@chromium.org, Nov 22 2017

Status: Archived (was: Assigned)
►

Sign in to add a comment