CmdError: Command <ls /sys/devices/system/cpu/cpu*/cpufreq/cpuinfo_max_freq> failed, rc=2, Command returned non-zero exit status |
|||||
Issue description
The following message appears in many, if not all autotests during VMTests:
Traceback (most recent call last):
File "/usr/local/autotest/common_lib/log.py", line 70, in decorated_func
fn(*args, **dargs)
File "/usr/local/autotest/bin/base_sysinfo.py", line 374, in log_before_each_iteration
board = utils.get_board_with_frequency_and_memory()
File "/usr/local/autotest/bin/site_utils.py", line 864, in get_board_with_frequency_and_memory
frequency = int(round(get_cpu_max_frequency() * 1e-8)) * 0.1
File "/usr/local/autotest/bin/site_utils.py", line 788, in get_cpu_max_frequency
paths = _get_cpufreq_paths('cpuinfo_max_freq')
File "/usr/local/autotest/bin/site_utils.py", line 925, in _get_cpufreq_paths
paths = utils.run(cmd, verbose=False).stdout.splitlines()
File "/usr/local/autotest/common_lib/base_utils.py", line 893, in run
"Command returned non-zero exit status")
CmdError: Command <ls /sys/devices/system/cpu/cpu*/cpufreq/cpuinfo_max_freq> failed, rc=2, Command returned non-zero exit status
* Command:
ls /sys/devices/system/cpu/cpu*/cpufreq/cpuinfo_max_freq
Some recent examples:
login_OwnershipTaken FAILED on x86-generic-paladin R51-8062.0.0-rc1:
https://build.chromium.org/p/chromiumos/builders/x86-generic-paladin/builds/25635/steps/VMTest%20%28attempt%201%29/logs/stdio
https://storage.cloud.google.com/chromeos-image-archive/x86-generic-paladin/R51-8062.0.0-rc1/vm_test_results_1/test_harness/failed/SimpleTestVerify/1_autotest_tests/results-22-login_OwnershipTaken/login_OwnershipTaken/debug/login_OwnershipTaken.DEBUG
login_OwnershipTaken PASSED on x86-generic-paladin R51-8062.0.0-rc2:
https://pantheon.corp.google.com/storage/browser/chromeos-image-archive/x86-generic-paladin/R51-8062.0.0-rc2/vm_test_results_1/test_harness/all/SimpleTestVerify/1_autotest_tests/results-22-login_OwnershipTaken/login_OwnershipTaken/debug
,
Mar 16 2016
The following revision refers to this bug: https://chromium.googlesource.com/chromiumos/third_party/autotest/+/c73f316cc4663aacd2422397072cb3562e95d50a commit c73f316cc4663aacd2422397072cb3562e95d50a Author: Ilja H. Friedel <ihf@chromium.org> Date: Tue Mar 15 04:34:45 2016 site_utils: detect VM for board name. Also pylint cleanup. BUG=chromium:594569 TEST=Ran locally on lars. Change-Id: I2368220c1a67d139af083b3d167d76f45e66e8eb Reviewed-on: https://chromium-review.googlesource.com/332682 Commit-Ready: Ilja Friedel <ihf@chromium.org> Tested-by: Ilja Friedel <ihf@chromium.org> Reviewed-by: Stéphane Marchesin <marcheu@chromium.org> [modify] https://crrev.com/c73f316cc4663aacd2422397072cb3562e95d50a/client/bin/site_utils.py
,
Mar 17 2016
03/16 17:19:44.641 INFO | base_sysinfo:0375| ChromeOS BOARD = rambi_VM
,
Mar 29 2016
Didn't work for all boards. Will follow some more tricks here http://www.dmo.ca/blog/detecting-virtualization-on-linux/
,
Jul 1 2016
A builder saw it again: in https://uberchromegw.corp.google.com/i/chromeos/builders/lakitu-paladin/builds/3610 GCE tests fail: https://pantheon.corp.google.com/storage/browser/chromeos-image-archive/lakitu-paladin/R53-8528.0.0-rc1/gce_test_results_2/test_harness/failed/SimpleTestVerify/2_autotest_tests/suite_gce-smoke/results-11-cloud_Toolbox/debug/ CmdError: Command <ls /sys/devices/system/cpu/cpu*/cpufreq/cpuinfo_max_freq> failed, rc=2, Command returned non-zero exit status "ls: cannot access /sys/devices/system/cpu/cpu*/cpufreq/cpuinfo_max_freq: No such file or directory" I don't understand why it also failed in the test before but did not trigger a test failure.
,
Jul 1 2016
I will look at this tomorrow.
,
Aug 8 2016
I believe this cpufreq message occurs on lakitu, but isn't the cause of the build failures.
For example from c#5 I believe the real failure is:
START ---- ---- timestamp=1467331998 localtime=Jul 01 00:13:18
START cloud_Toolbox cloud_Toolbox timestamp=1467331998 localtime=Jul 01 00:13:18
ERROR cloud_Toolbox cloud_Toolbox timestamp=1467332015 localtime=Jul 01 00:13:35 Command <toolbox echo hello world> failed, rc=1, Command returned non-zero exit status
* Command:
toolbox echo hello world
Exit status: 1
Duration: 15.4814138412
stderr:
Error response from daemon: Get https://registry-1.docker.io/v2/library/debian/manifests/latest: Get https://auth.docker.io/token?scope=repository%3Alibrary%2Fdebian%3Apull&service=registry.docker.io: net/http: request canceled (Client.Timeout exceeded while awaiting headers)
END ERROR cloud_Toolbox cloud_Toolbox timestamp=1467332015 localtime=Jul 01 00:13:35
END GOOD ---- ---- timestamp=1467332017 localtime=Jul 01 00:13:37
,
Dec 26 2017
,
Jan 2 2018
[It appears that a bunch of old cros issues bulk-added the "Infra" component recently, but they should probably be "Infra>Client>ChromeOS".] |
|||||
►
Sign in to add a comment |
|||||
Comment 1 by ihf@chromium.org
, Mar 15 2016Owner: ihf@chromium.org
Status: Started (was: Available)