valgrind is generating different ptest results between the core-image-sato and core-image-sato-sdk images. Specifically: core-image-sato: https://autobuilder.yocto.io/pub/non-release/20190417-10/testresults/qemux86-64-ptest/testresults.json Recipe | Passed | Failed | Skipped | valgrind | 0 | 0 | 0 | core-image-sato-sdk: https://autobuilder.yocto.io/pub/non-release/20190417-14/testresults/qemux86-64-ptest/testresults.json Recipe | Passed | Failed | Skipped | valgrind | 297 | 251 | 31 | Not that no tests are reported at all in core-image-sato
Created attachment 4507 [details] ptest log from core-image-sato build
Created attachment 4508 [details] ptest log from core-image-sato-sdk build
Created attachment 4557 [details] ptest log from core-image-minimal build
I've done the work to make the tests independent of the image. I've also enable ~500 more tests, most of which pass. On qemuarm64, some tests are causing valgrind to segfault and since the valgrind test perl script doesn't reap defunct processes, it eventually causes the oom-killer to run. I'm working on fixing the arm64 bug or if that takes too long, I'll skip the problematic tests and send the patches that I have.
Sent to list: http://lists.openembedded.org/pipermail/openembedded-core/2019-September/286810.html https://patchwork.openembedded.org/series/19821/
Fixed by: http://git.openembedded.org/openembedded-core/commit/?id=6dbaaeec17eae8329031188b688b33306a871870 and the two previous commits. Test results from master-next that includes this work: https://autobuilder.yocto.io/pub/non-release/20190916-9/testresults/testresult-report.txt There is more work to do for arm64 and likely other arches. The arm64 problems are tracked by: https://bugzilla.yoctoproject.org/show_bug.cgi?id=13520