bash: /usr/local/autotest/result_tools/utils.py: No such file or directory |
||
Issue descriptionThe following error is reported from every cheets_CTS_N runs. I guess this is happening since https://chromium-review.googlesource.com/584864. For instance: https://pantheon.corp.google.com/storage/browser/chromeos-autotest-results/137043987-chromeos-test/chromeos4-row11-rack9-host11/debug/ 08/24 17:30:30.808 DEBUG| abstract_ssh:0620| Host chromeos4-row11-rack9-host11 is now up 08/24 17:30:30.808 DEBUG| runner:0089| result tools are already deployed to chromeos4-row11-rack9-host11. 08/24 17:30:30.809 DEBUG| runner:0100| Getting directory summary for /usr/local/autotest/results/default 08/24 17:30:30.818 DEBUG| ssh_host:0296| Running (ssh) '/usr/local/autotest/result_tools/utils.py -p /usr/local/autotest/results/default -m 307200' from '_process_line|collect_client_job_results|run_on_client|run|wrapper|run_very_slowly' 08/24 17:30:31.027 ERROR| utils:0280| [stderr] bash: /usr/local/autotest/result_tools/utils.py: No such file or directory 08/24 17:30:31.069 ERROR| runner:0121| Non-critical failure: Failed to create directory summary for /usr/local/autotest/results/default. Traceback (most recent call last): File "/usr/local/autotest/client/bin/result_tools/runner.py", line 114, in run_on_client timeout=_BUILD_DIR_SUMMARY_TIMEOUT) File "/usr/local/autotest/server/hosts/ssh_host.py", line 316, in run return self.run_very_slowly(*args, **kwargs) File "/usr/local/autotest/site-packages/chromite/lib/metrics.py", line 482, in wrapper return fn(*args, **kwargs) File "/usr/local/autotest/server/hosts/ssh_host.py", line 307, in run_very_slowly ssh_failure_retry_ok) File "/usr/local/autotest/server/hosts/ssh_host.py", line 258, in _run raise error.AutoservRunError("command execution error", result) AutoservRunError: command execution error * Command: /usr/bin/ssh -a -x -o StrictHostKeyChecking=no -o UserKnownHostsFile=/dev/null -o BatchMode=yes -o ConnectTimeout=30 -o ServerAliveInterval=900 -o ServerAliveCountMax=3 -o ConnectionAttempts=4 -o Protocol=2 -l root -p 22 chromeos4-row11-rack9-host11 "export LIBC_FATAL_STDERR_=1; if type \"logger\" > /dev/null 2>&1; then logger -tag \"autotest\" \"server[stack::run_on_client|run|wrapper] -> ssh_run(/usr/local/autotest/result_tools/utils.py -p /usr/local/autotest/results/default -m 307200)\";fi; /usr/local/autotest/result_tools/utils.py -p /usr/local/autotest/results/default -m 307200" Exit status: 127 Duration: 0.216740131378 stderr: bash: /usr/local/autotest/result_tools/utils.py: No such file or directory
,
Aug 25 2017
The failure is caused by test operation that removed previously deployed result_tools. We try to copy result_tools to dut only once across the test, it seems that the test did some cleanup which breaks the assumption. I will add some error handling and retry here. It's a non-critical failure. The only impact is that autotest thinks some results are on server side rather than client side. Since cheets test have a large enough result size config, it really doesn't matter much.
,
Aug 25 2017
The following revision refers to this bug: https://chromium.googlesource.com/chromiumos/third_party/autotest/+/86de0941a54aabcbb278e49b013eb831f54b1f9d commit 86de0941a54aabcbb278e49b013eb831f54b1f9d Author: Dan Shi <dshi@google.com> Date: Fri Aug 25 19:09:03 2017 [autotest] Don't delete result_tools when installing autotest using package result_tools is deployed during test run, there is no need to re-deploy it. BUG= chromium:758799 TEST=run client dummy test. Change-Id: Icb6babb656a47c0b86a82e7609193ef24c988c87 Reviewed-on: https://chromium-review.googlesource.com/634645 Commit-Ready: Dan Shi <dshi@google.com> Tested-by: Dan Shi <dshi@google.com> Reviewed-by: Dan Shi <dshi@google.com> [modify] https://crrev.com/86de0941a54aabcbb278e49b013eb831f54b1f9d/server/autotest.py [modify] https://crrev.com/86de0941a54aabcbb278e49b013eb831f54b1f9d/server/autotest_unittest.py
,
Jan 26 2018
I believe this is fixed |
||
►
Sign in to add a comment |
||
Comment 1 by kinaba@chromium.org
, Aug 25 2017