STATUS: IDLE BUILD: 2.1_M3.RC1: 8debfea81e69d038bd2d56314b272cb74f5582ed ENVIRONMENT: genericx86-64-WIC on NUC STEPS TO REPRODUCE: Parse dmesg log and all log files in /var/log for keywords like: "error" , "failed" , "cannot", "can't" etc. Filter out the known and invalid errors or errors that appear in certain situations and need to be ignored. EXPECTED OUTCOME: No errors or fails should be present in logs ACTUAL OUTCOME The next error messages are displayed: FAIL: test_parselogs (oeqa.runtime.parselogs.ParseLogsTest) Central error: [ 0.092241] pmd_set_huge: Cannot satisfy [mem 0xf8000000-0xf8200000] with a huge-page mapping due to MTRR override. Central error: [ 0.092241] pmd_set_huge: Cannot satisfy [mem 0xf8000000-0xf8200000] with a huge-page mapping due to MTRR override. | FAIL: test_rpm_query_nonroot (oeqa.runtime.rpm.RpmInstallRemoveTest) | FAIL: test_smart_info (oeqa.runtime.smart.SmartBasicTest) FAIL: test_smart_query (oeqa.runtime.smart.SmartBasicTest) FAIL: test_smart_add_rpmdir (oeqa.runtime.smart.SmartRepoTest) FAIL: test_smart_install (oeqa.runtime.smart.SmartRepoTest) FAIL: test_smart_install_from_disk (oeqa.runtime.smart.SmartRepoTest) FAIL: test_smart_install_from_http (oeqa.runtime.smart.SmartRepoTest) FAIL: test_smart_local_dir (oeqa.runtime.smart.SmartRepoTest) | FAIL: test_smart_remote_repo (oeqa.runtime.smart.SmartRepoTest) FAIL: test_smart_remove_package (oeqa.runtime.smart.SmartRepoTest) FAILED (failures=11, skipped=9) | DEBUG: Python function do_testimage finished | ERROR: Function failed: core-image-sato-sdk - FAILED - check the task log and the ssh log ERROR: Task 0 (/home/fjpedraz/YP-2.1_M3.rc1/poky/meta/recipes-sato/images/core-image-sato-sdk.bb, do_testimage) failed with exit code '1' NOTE: Tasks Summary: Attempted 1 tasks of which 0 didn't need to be rerun and 1 failed.
Created attachment 3033 [details] losWicWeekly
FAILED ON WIC WEEKLY genericx86-64 NUC D54250WYK
More investigation is needed to verify if this is a QA setup issue or a real SMART issue. Please confirm it's reproducible.
This was caused because the firmware on the platforms was not up to date. another bug 9434 is used to track issues with the new firmware.