android duts used in test_push should be not moved around |
||||||
Issue description
test_push always failed due to android duts used in test_push were removed from the testbed. Example:
03/22 14:13:04.310 DEBUG| adb_host:0397| Command: timeout --signal=9 3601 adb -s 84B7N16625000220 get-state
03/22 14:13:04.310 DEBUG| ssh_host:0284| Running (ssh) 'timeout --signal=9 3601 adb -s 84B7N16625000220 get-state'
03/22 14:13:04.496 ERROR| base_utils:0280| [stderr] error: device '84B7N16625000220' not found
03/22 14:13:04.499 ERROR| verify:0031| command execution error
* Command:
/usr/bin/ssh -a -x -t -o ControlPath=/tmp/_autotmp_6bss8yssh-
master/socket -o StrictHostKeyChecking=no -o
UserKnownHostsFile=/tmp/tmpHpYpbI -o BatchMode=yes -o ConnectTimeout=30 -o
ServerAliveInterval=300 -l root -p 22 android1758-row1-rack7-test-
station-4.cros " if type \"logger\" > /dev/null 2>&1; then logger -tag
\"autotest\" \"server[stack::adb_run|_device_run|run] -> ssh_run(timeout
--signal=9 3601 adb -s 84B7N16625000220 get-state)\";fi; timeout
--signal=9 3601 adb -s 84B7N16625000220 get-state"
Exit status: 1
Duration: 0.147535085678
stderr:
error: device '84B7N16625000220' not found
Traceback (most recent call last):
File "/usr/local/autotest/server/control_segments/verify", line 27, in verify
target.verify()
File "/usr/local/autotest/server/hosts/testbed.py", line 176, in verify
device.verify()
File "/usr/local/autotest/client/common_lib/hosts/base_classes.py", line 316, in verify
self.verify_connectivity()
File "/usr/local/autotest/server/hosts/adb_host.py", line 873, in verify_connectivity
if not self.is_device_ready():
File "/usr/local/autotest/server/hosts/adb_host.py", line 863, in is_device_ready
desc='Waiting for device state to be `device`')
File "/usr/local/autotest/client/common_lib/site_utils.py", line 965, in poll_for_condition
value = condition()
File "/usr/local/autotest/server/hosts/adb_host.py", line 861, in <lambda>
lambda: self.adb_run('get-state').stdout.strip() == 'device',
File "/usr/local/autotest/server/hosts/adb_host.py", line 301, in adb_run
return self._device_run(ADB_CMD, command, **kwargs)
File "/usr/local/autotest/server/hosts/adb_host.py", line 403, in _device_run
connect_timeout=connect_timeout, args=args)
File "/usr/local/autotest/server/hosts/teststation_host.py", line 136, in run
return super(TestStationHost, self).run(cmd, *args, **dargs)
File "/usr/local/autotest/server/hosts/ssh_host.py", line 295, in run
ssh_failure_retry_ok)
File "/usr/local/autotest/server/hosts/ssh_host.py", line 252, in _run
raise error.AutoservRunError("command execution error", result)
AutoservRunError: command execution error
* Command:
/usr/bin/ssh -a -x -t -o ControlPath=/tmp/_autotmp_6bss8yssh-
master/socket -o StrictHostKeyChecking=no -o
UserKnownHostsFile=/tmp/tmpHpYpbI -o BatchMode=yes -o ConnectTimeout=30 -o
ServerAliveInterval=300 -l root -p 22 android1758-row1-rack7-test-
station-4.cros " if type \"logger\" > /dev/null 2>&1; then logger -tag
\"autotest\" \"server[stack::adb_run|_device_run|run] -> ssh_run(timeout
--signal=9 3601 adb -s 84B7N16625000220 get-state)\";fi; timeout
--signal=9 3601 adb -s 84B7N16625000220 get-state"
Exit status: 1
Duration: 0.147535085678
,
Mar 23 2017
,
Mar 23 2017
serial 84B7N16625000220 was removed from that testbed long time ago. I just checked the system, both testbeds are working now. Also, both duts are locked in cautotest.
,
Mar 23 2017
I manually updated chromeos-autotest.hot to use the available DUTs in testbed. What I did yesterday: 1. login into chromeos-autotest.hot 2. $ ssh android1758-row1-rack7-test-station-4.cros 3. $ adb devices -l 4. Find the available angler DUT 5. Replace the missing one with the one just found 6. Kick off verify on testbed DUTs.
,
Mar 23 2017
oops, that's not the right way. We can't randomly pick serials. For the ones not working, we need to ask lab to repair them. Let me find the serials on cautotest and clean it up.
,
Mar 23 2017
Oh, ok.
,
Mar 23 2017
My fault.
,
Mar 28 2018
This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue. Sorry for the inconvenience if the bug really should have been left as Available. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Aug 3
This bug has an owner, thus, it's been triaged. Changing status to "assigned". |
||||||
►
Sign in to add a comment |
||||||
Comment 1 by shuqianz@chromium.org
, Mar 23 2017