With plain poky genericarm64 image “core-image-base”, parselogs oeqa runtime tests is failing due to some extra warnings from kernel at boot.
There is an “ignorelist” infra in yocto to ignore certain machine specific warnings which we don’t care about, but those files are currently not exported to “bitbake -c testexport core-image-base” tar ball and thus simply adding the kernel messages to correct ignore list doesn’t fix this.
Refactor the testexport.bbclass to also export tests from non-core poky/meta paths and these should include the parselogs ignore files. Then make sure these exported layer paths get used at test execution time.
Another side effect of this is that with meta-arm builds which include TPM and fTPM support for the machine/image, then “ftpm” oeqa runtime test is not exported to “testexport.bbclass” tar ball and thus doesn’t even run.
Medium
With plain poky genericarm64 image “core-image-base”, parselogs oeqa runtime tests is failing due to some extra warnings from kernel at boot.
There is an “ignorelist” infra in yocto to ignore certain machine specific warnings which we don’t care about, but those files are currently not exported to “bitbake -c testexport core-image-base” tar ball and thus simply adding the kernel messages to correct ignore list doesn’t fix this.
Refactor the testexport.bbclass to also export tests from non-core poky/meta paths and these should include the parselogs ignore files. Then make sure these exported layer paths get used at test execution time.
Another side effect of this is that with meta-arm builds which include TPM and fTPM support for the machine/image, then “ftpm” oeqa runtime test is not exported to “testexport.bbclass” tar ball and thus doesn’t even run.