| Message ID | 20260312080200.2132060-1-mikko.rapeli@linaro.org |
|---|---|
| State | New |
| Headers | show |
| Series | [yocto-autobuilder-helper,RFC] config.json: enable qemu based testimage testing of genericarm64 core-image-sato | expand |
diff --git a/config.json b/config.json index 1a8284cdcb70..2a2d5b62f948 100644 --- a/config.json +++ b/config.json @@ -783,7 +783,14 @@ }, "genericarm64-alt" : { "MACHINE" : "genericarm64", - "TEMPLATE" : "altcfg-hw" + "TEMPLATE" : "altcfg-hw", + "step1" : { + "BBTARGETS" : "core-image-full-cmdline core-image-sato core-image-sato-sdk" + }, + "step2" : { + "BBTARGETS" : "core-image-sato", + "SANITYTARGETS" : "core-image-sato:do_testimage" + } }, "genericx86" : { "MACHINE" : "genericx86",
RFC: not sure how stable the tests are with tap networking and full graphics stack on AB infra. Depends on genericarm64 testimage.bbclass fixes from https://lists.yoctoproject.org/g/poky/message/13862 qemu is one of the devices supported by genericarm64 machine. For qemu, u-boot is used as the UEFI firmware. All of the oeqa runtime tests run by testimage.bbclass have been passing in my testing for a long time so they should be stable and working on AB infrastructure as well. Testing only core-image-sato to avoid adding too much load to test infra and since it has good enough coverage for now. Real target HW testing on AMD KV260 is run by us on weekly basis and reports are posted to automated-testing list: https://lists.yoctoproject.org/g/automated-testing/message/1547 These flash and boot the same core-image-sato image and run the same oeqa runtime tests but via testexport.bbclass since test lab workers are not full yocto build machines. Additionally I run the same tests on AMD zcu102, Rockchip rockpi4b, Raspberry Pi 4, TI BeaglePlay, NXP i.MX8MP Verdin and Renesas SMARC EVK boards. Signed-off-by: Mikko Rapeli <mikko.rapeli@linaro.org> --- config.json | 9 ++++++++- 1 file changed, 8 insertions(+), 1 deletion(-)