kernel_ConfigVerify failed on Caroline-tot-chrome-pfq-informational |
|
Issue descriptionkernel_ConfigVerify is failing on Caroline-tot-chrome-pfq-informational https://cros-goldeneye.corp.google.com/chromeos/healthmonitoring/buildDetails?buildbucketId=8945895295425528768 Trace: 05/21 15:06:55.458 WARNI| test:0637| The test failed with the following exception Traceback (most recent call last): File "/usr/local/autotest/common_lib/test.py", line 631, in _exec _call_test_function(self.execute, *p_args, **p_dargs) File "/usr/local/autotest/common_lib/test.py", line 831, in _call_test_function return func(*args, **dargs) File "/usr/local/autotest/common_lib/test.py", line 495, in execute dargs) File "/usr/local/autotest/common_lib/test.py", line 362, in _call_run_once_with_retry postprocess_profiled_run, args, dargs) File "/usr/local/autotest/common_lib/test.py", line 400, in _call_run_once self.run_once(*args, **dargs) File "/usr/local/autotest/tests/kernel_ConfigVerify/kernel_ConfigVerify.py", line 257, in run_once raise error.TestFail((", ".join(config.failures()))) TestFail: "CONFIG_ESD_FS" found for "CONFIG_.*_FS$" when only "CONFIG_SCSI_PROC_FS|CONFIG_EXT4_FS|CONFIG_UDF_FS|CONFIG_HFSPLUS_FS|CONFIG_ISO9660_FS|CONFIG_DEBUG_FS|CONFIG_PROC_FS|CONFIG_USB_CONFIGFS_F_FS|CONFIG_USB_F_FS|CONFIG_VFAT_FS|CONFIG_NFS_FS|CONFIG_EXT4_USE_FOR_EXT23|CONFIG_SND_PROC_FS|CONFIG_FAT_FS|CONFIG_CONFIGFS_FS|CONFIG_ECRYPT_FS|CONFIG_FUSE_FS" allowed Log link: https://00e9e64bac5d0cc943fdce557598c063427477d02cc56cbe3d-apidata.googleusercontent.com/download/storage/v1/b/chromeos-autotest-results/o/201801919-chromeos-test%2Fchromeos6-row4-rack23-host17%2Fdebug%2Fclient.0.DEBUG?qk=AD5uMEsNgEnGO0Rc3aZzaJ65Ca0d7-kIqWVvKPJorfk7t2ytkxJLViJkjTJf8MeLhnoyZl0vfJmeB5Oc-0ELQyxIMmrdYjdbyEnQmlk8qu7sPAmqyrl2zXkpWXCgstPedkANMvcueCJr40Be09gkLRDlJ-Riu3GiagwwnF19FzjKi_3_iFUPUn9EgglGSnFKUoSjdGvfVWrvec_bzLas3n1t86fpKIQrqdR2gBwb7iQ6VjDImPfkdYOYRasjBij_WO8Z4V-iO5qbAfrz5WP7J1meXH8b8dlvaP1yBhFOhORM11i0LeHesIGfmq7XiQFTJfisZTsqGZ4gbuQP_qMGBEEVKSrthQoJdu955QEb6kSQrSNdcq0XIa9vKyFEmv6BKV3UtYZNCgwD0EfzUafCbkiL2FZbNbQ3S9EIxM1vSdTSCh9Gw4KZOYORKHhKu9yfw8S28NINyz1lYZznXyNJO0by5xWgJgZwyNTMWM1DX9pvNxCVb7vpaHLFaxFg-4zc_cHlz6n7Clx1kOKNrcZYwh0UUm1JCdIe3VemTmM2ST0YsGoU7fp3laURaz1ZMeZkgJWDtCvVK4fTW3-vn0uQ33Wnf_cHdkp9XSVx9cH2GVwyP82jpL1SSJ3_zWGZ4e1roi8m84NzkN8L9iuyZkIYKBnwrpEyaR5LNBUSm-ZRW-tuTTq06o3G19onXXXHkp475R_Wfn8ukjSVBxSNeQYnCj7Ib6P9kwEzisVrwHmSzAqI6yw0QxkG-iI4cNPean0D6yufjjgt2elHVoGlX3R14-vZUz41utzElyPj6GVc2xcZ1kyLfP82Y_1c1QfmhEpeHkUOX_iQfrYnEMq-uYXN425xp3q3YUlZVw This seems to be related to https://b.corp.google.com/issues/63876697#comment101 +Sheriffs
,
May 22 2018
We believe this will be resolved by https://chromium-review.googlesource.com/c/chromiumos/third_party/kernel/+/1068157 and the long term fix and reland should be done soon also. |
|
►
Sign in to add a comment |
|
Comment 1 by xiaoyinh@chromium.org
, May 22 2018