Created attachment 3812 [details] log.do_testimage_Minnowmax64 STATUS: IDLE BUILD: 2.1.3: rc1-fe7fb002216f7886d49942333ea6d8592339bb05 ENVIRONMENT: genericx86-64-WIC on MMAX64 and NUC6i5SYH Build Configuration: BB_VERSION = "1.30.0" BUILD_SYS = "x86_64-linux" NATIVELSBSTRING = "universal" TARGET_SYS = "x86_64-poky-linux" MACHINE = "genericx86-64" DISTRO = "poky" DISTRO_VERSION = "2.1.3" TUNE_FEATURES = "m64 core2" TARGET_FPU = "" meta meta-poky meta-yocto-bsp = "HEAD:fe7fb002216f7886d49942333ea6d8592339bb05" STEPS TO REPRODUCE: 1.- Clone poky and setup to run BSP automated test: https://wiki.yoctoproject.org/wiki/Quality_Assurance_yocto_project#Steps_for_BSP_Automated_Testing 2.- Download and burn "mkefidisk-201706062011-sda.direct" image from: https://autobuilder.yocto.io/srv/autobuilder/autobuilder.yoctoproject.org/pub/releases/yocto-2.1.3.rc1/machines/genericx86-64/ 3.- Boot the image in Minnowmax 64 and run: $ bitbake core-image-sato-sdk -c testimage EXPECTED OUTCOME: All the tests successfully PASS ACTUAL OUTCOME: FAIL: test_syslog_running (oeqa.runtime.syslog.SyslogTest) FAIL: test_connmand_running (oeqa.runtime.connman.ConnmanTest) FAIL: test_xorg_running (oeqa.runtime.xorg.XorgTest) FAIL: test_perl_exists (oeqa.runtime.perl.PerlTest) FAIL: test_perl_works (oeqa.runtime.perl.PerlTest) FAIL: test_gcc_compile (oeqa.runtime.gcc.GccCompileTest) FAIL: test_gpp2_compile (oeqa.runtime.gcc.GccCompileTest) FAIL: test_gpp_compile (oeqa.runtime.gcc.GccCompileTest) FAIL: test_make (oeqa.runtime.gcc.GccCompileTest) FAIL: test_ldd_exists (oeqa.runtime.ldd.LddTest) FAILED (failures=10, skipped=5) NOTE: same errors/skipped for Minnowx64 and NUC Full logs attached.
Created attachment 3813 [details] log.do_test_nuc
I found this in genericx86-WIC on MMAX32 error log attached
Created attachment 3814 [details] LOG_MM32
wic images are not suppose to be generated on Krogoth so this issue is invalid see also bug 11637 for more details.
The errors show the following information: self.assertEqual(status, 0, msg="no syslogd process, ps output: %s" % self.target.run(oeRuntimeTest.pscmd)[1]) AssertionError: 1 != 0 : no syslogd process, ps output: ps: invalid option -- 'e' BusyBox v1.24.1 (2017-06-06 18:04:10 UTC) multi-call binary. Usage: ps So this is saying that ps does not recognize the option "-e" for the command ps, and this is caused becuase the command ps (from busybox) does not support that option. The command is declared on the oetest class as (on Krogoth): setattr(oeRuntimeTest, "pscmd", "ps -ef" if oeTest.hasPackage("procps") else "ps") Whereas on master is declared as: cmd = '%s | grep -i [s]yslogd' % self.tc.target_cmds['ps'] Which does not causes an issue, so this has either been fixed already (which would imply a backport from master), or the testcase was not run correctly.
WIC images are not tested on Krogoth, closing this one.
Verified.