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

Issue 839743 link

Starred by 1 user

Issue metadata

Status: Fixed
Owner:
Closed: May 2018
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 1
Type: Bug



Sign in to add a comment

lakitu cq failures: vm test failures on kernel config

Project Member Reported by coconutruben@chromium.org, May 4 2018

Issue description

https://uberchromegw.corp.google.com/i/chromeos/builders/lakitu-gpu-paladin
https://uberchromegw.corp.google.com/i/chromeos/builders/lakitu-st-paladin
https://uberchromegw.corp.google.com/i/chromeos/builders/lakitu-paladin

All failed now after good runs previously, with this error pattern (redacted for easier readability):

Ed, can you take a look, as some of your CLs have already landed, while others were in flight for this run:
autotest-lakitu | edjee | *619775 | kernel_LakituConfigVerify: allow CONFIG_EFIVAR_FS
board-overlays | edjee | 1041012 | lakitu: lakitu-kernel-4_14: enable efivarfs
being the ones in flight

/tmp/cbuildbotZWacG2/smoke/test_harness/all/SimpleTestVerify/1_autotest_tests/results-13-kernel_LakituConfigVerify                                         FAIL: "CONFIG_POWER_SUPPLY" was "y" (wanted one of "unset") in kernel config
kernel_LakituConfigVerify             [  FAILED  ]
FAIL: "CONFIG_POWER_SUPPLY" was "y" (wanted one of "unset") in kernel config
05/04 08:26:27.155 ERROR|               log:0027| pre-test siteration sysinfo error:
05/04 08:26:27.158 ERROR|         traceback:0013| Traceback (most recent call last):
05/04 08:26:27.162 ERROR|         traceback:0013|   File "/usr/local/autotest/common_lib/log.py", line 25, in decorated_func
05/04 08:26:27.165 ERROR|         traceback:0013|     fn(*args, **dargs)
05/04 08:26:27.168 ERROR|         traceback:0013|   File "/usr/local/autotest/bin/base_sysinfo.py", line 394, in log_before_each_iteration
05/04 08:26:27.172 ERROR|         traceback:0013|     board = utils.get_board_with_frequency_and_memory()
05/04 08:26:27.175 ERROR|         traceback:0013|   File "/usr/local/autotest/bin/utils.py", line 2052, in get_board_with_frequency_and_memory
05/04 08:26:27.178 ERROR|         traceback:0013|     frequency = int(round(get_cpu_max_frequency() * 1e-8)) * 0.1
05/04 08:26:27.181 ERROR|         traceback:0013|   File "/usr/local/autotest/bin/utils.py", line 1879, in get_cpu_max_frequency
05/04 08:26:27.185 ERROR|         traceback:0013|     paths = _get_cpufreq_paths('cpuinfo_max_freq')
05/04 08:26:27.188 ERROR|         traceback:0013|   File "/usr/local/autotest/bin/utils.py", line 2136, in _get_cpufreq_paths
05/04 08:26:27.192 ERROR|         traceback:0013|     paths = utils.run(cmd, verbose=False).stdout.splitlines()
05/04 08:26:27.195 ERROR|         traceback:0013|   File "/usr/local/autotest/common_lib/utils.py", line 748, in run
05/04 08:26:27.200 ERROR|         traceback:0013|     "Command returned non-zero exit status")
05/04 08:26:27.204 ERROR|         traceback:0013| CmdError: Command <ls /sys/devices/system/cpu/cpu*/cpufreq/cpuinfo_max_freq> failed, rc=2, Command returned non-zero exit status
05/04 08:26:27.207 ERROR|         traceback:0013| * Command:
ERROR|         traceback:0013|     ls /sys/devices/system/cpu/cpu*/cpufreq/cpuinfo_max_freq
ERROR|         traceback:0013| Exit status: 2
ERROR|         traceback:0013| Duration: 0.00161910057068
ERROR|         traceback:0013|
ERROR|         traceback:0013| stderr:
ERROR|         traceback:0013| ls: cannot access '/sys/devices/system/cpu/cpu*/cpufreq/cpuinfo_max_freq': No such file or directory
ERROR|     kernel_config:0019| FAIL: "CONFIG_POWER_SUPPLY" was "y" (wanted one of "unset") in kernel config

 
Cc: coconutruben@chromium.org
Owner: edjee@google.com

Comment 3 by warx@chromium.org, May 7 2018

Cc: -warx@chromium.org sammiequon@chromium.org
Status: Fixed (was: Available)
Marking as fixed, as it hasn't shown in latest runs

Sign in to add a comment