Historically, we build a VM for each individual tests we wanted to run. At the end of the day, all tests are available within the VM and it is just a matter of what we did put in our init script.
With kernel-patches/vmtest#139 we can now pass the test to run as a command line argument at boot time. So, the run-qemu step will need to provide that test name.
Historically, we build a VM for each individual tests we wanted to run. At the end of the day, all tests are available within the VM and it is just a matter of what we did put in our init script. With kernel-patches/vmtest#139 we can now pass the test to run as a command line argument at boot time. So, the run-qemu step will need to provide that test name.
tested with an unmodified kernel-patches/vmtest: https://github.com/kernel-patches/vmtest/pull/171/checks and a modified one (e.g building the rootfs vm after building the kernel and providing the test on the boot command): https://github.com/kernel-patches/vmtest/actions/runs/3432974206/jobs/5723083313