[PATCH 3/4] genericarm64.conf: add "testimage" and "testexport" to default IMAGE_CLASSES
Mikko Rapeli <[email protected]>
| Newsgroups | org.yoctoproject.lists.poky |
|---|---|
| Message-ID | <[email protected]> |
They export oeqa runtime tests from build environment so that they can be run in test environment with real HW. Once device has been flashed and booted so that SSH is available and tmp/testimage is available on the test worker, then tests can be run with: $ ./oe-test runtime --target-type simpleremote \ --target-ip 10.0.0.2 Sample test run log from AMD Kria KV260 board managed by Linaro Automated Validation Architecture (LAVA, https://www.lavasoftware.org/ ) lab: https://ledge.validation.linaro.org/scheduler/job/95628 Signed-off-by: Mikko Rapeli <[email protected]> --- meta-yocto-bsp/conf/machine/genericarm64.conf | 3 +++ 1 file changed, 3 insertions(+) diff --git a/meta-yocto-bsp/conf/machine/genericarm64.conf b/meta-yocto-bsp/conf/machine/genericarm64.conf index a77ffb0431..a81e4e2689 100644 --- a/meta-yocto-bsp/conf/machine/genericarm64.conf +++ b/meta-yocto-bsp/conf/machine/genericarm64.conf @@ -35,6 +35,9 @@ SERIAL_CONSOLES ?= "115200;ttyPS0 115200;ttyPS1 115200;ttyAMA0 115200;hvc0 11520 # of this machine is that real hardware comes with the firmware pre-loaded. UBOOT_MACHINE = "qemu_arm64_defconfig" +# Run oeqa runtime tests outside of the build environment +IMAGE_CLASSES += "testimage testexport" + # runqemu configuration to run a genericarm64 image inside a qemu-system-aarch64. You will need # to build u-boot explicitly. IMAGE_CLASSES += "qemuboot" -- 2.34.1