| Message ID | 20241029080544.5486-3-mikko.rapeli@linaro.org (mailing list archive) |
|---|---|
| State | New |
| Headers | show |
| Series | [1/4] README.hardware.md: add genericarm64 maintainers | expand |
On 29 Oct 2024, at 08:05, Mikko Rapeli via lists.yoctoproject.org <mikko.rapeli=linaro.org@lists.yoctoproject.org> wrote: > +# Run oeqa runtime tests outside of the build environment > +IMAGE_CLASSES += "testimage testexport" Sorry, but this isn’t appropriate for the machine configuration. The build configuration or distro can add these classes as needed. Ross
Hi, On Tue, Oct 29, 2024 at 11:57:28AM +0000, Ross Burton wrote: > On 29 Oct 2024, at 08:05, Mikko Rapeli via lists.yoctoproject.org <mikko.rapeli=linaro.org@lists.yoctoproject.org> wrote: > > +# Run oeqa runtime tests outside of the build environment > > +IMAGE_CLASSES += "testimage testexport" > > Sorry, but this isn’t appropriate for the machine configuration. The build configuration or distro can add these classes as needed. Ok but where do we do this for genericarm64 images? Somewhere in yocto-autobuilder2 or yocto-autobuilder-helper repos? I presume poky distro will not set these. Cheers, -Mikko
On 29 Oct 2024, at 12:05, Mikko Rapeli via lists.yoctoproject.org <mikko.rapeli=linaro.org@lists.yoctoproject.org> wrote: > On Tue, Oct 29, 2024 at 11:57:28AM +0000, Ross Burton wrote: >> On 29 Oct 2024, at 08:05, Mikko Rapeli via lists.yoctoproject.org <mikko.rapeli=linaro.org@lists.yoctoproject.org> wrote: >>> +# Run oeqa runtime tests outside of the build environment >>> +IMAGE_CLASSES += "testimage testexport" >> >> Sorry, but this isn’t appropriate for the machine configuration. The build configuration or distro can add these classes as needed. > > Ok but where do we do this for genericarm64 images? Somewhere in yocto-autobuilder2 > or yocto-autobuilder-helper repos? I presume poky distro will not set these. Is your intention to run testing over images generated by the autobuilder itself? Arguably, we should add these to poky.conf as poky is explicitly for testing purposes. Ross
Hi, On Tue, Oct 29, 2024 at 12:10:29PM +0000, Ross Burton wrote: > On 29 Oct 2024, at 12:05, Mikko Rapeli via lists.yoctoproject.org <mikko.rapeli=linaro.org@lists.yoctoproject.org> wrote: > > On Tue, Oct 29, 2024 at 11:57:28AM +0000, Ross Burton wrote: > >> On 29 Oct 2024, at 08:05, Mikko Rapeli via lists.yoctoproject.org <mikko.rapeli=linaro.org@lists.yoctoproject.org> wrote: > >>> +# Run oeqa runtime tests outside of the build environment > >>> +IMAGE_CLASSES += "testimage testexport" > >> > >> Sorry, but this isn’t appropriate for the machine configuration. The build configuration or distro can add these classes as needed. > > > > Ok but where do we do this for genericarm64 images? Somewhere in yocto-autobuilder2 > > or yocto-autobuilder-helper repos? I presume poky distro will not set these. > > Is your intention to run testing over images generated by the autobuilder itself? Arguably, we should add these to poky.conf as poky is explicitly for testing purposes. If these are enabled, then we could take the images and exported tests and run them directly in Lava lab devices. Another alternative is a different build with them enabled but then maybe limiting the amount of images would make sense. If you are ok with this, then I can propose this to poky defaults. Cheers, -Mikko
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"
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 <mikko.rapeli@linaro.org> --- meta-yocto-bsp/conf/machine/genericarm64.conf | 3 +++ 1 file changed, 3 insertions(+)