Enable kvm-unit-tests #1660
Enable kvm-unit-tests #1660
Conversation
broonie
force-pushed
the
kvm-unit-tests
branch
from
2c85224 to
1f997bd
Compare
|
This doesn't seem to be taking on staging - I'm assuming it's conflicting with something but any ideas what or how likely that is to progress? |
broonie
force-pushed
the
kvm-unit-tests
branch
from
1f997bd to
3faad96
Compare
There was a problem hiding this comment.
Please check #1753 , i am not sure if this particular PR have issue or PR 1753.
broonie
force-pushed
the
kvm-unit-tests
branch
4 times, most recently
from
f8629da to
3e70f99
Compare
|
We need Linaro/test-definitions#430 |
|
That's merged now, we just need a sync with upstream. |
broonie
force-pushed
the
kvm-unit-tests
branch
2 times, most recently
from
7ec17ca to
9c6c501
Compare
There was a problem hiding this comment.
No results on staging:
https://staging.kernelci.org/test/job/next/branch/master/kernel/next-20230331/
I've no idea why that is. @broonie Could you please take a look? It seems something is broken somewhere. I guess Jenkins logs on staging could provide additional information, and checking locally with kci_test that the jobs are getting generated.
|
This is the thing I keep on raising where the rootfs builds have started constantly failing due to what appears to be some sort of infra issue with running out of space in the target image during debos processing of Debian packages. We're using this in production internally FWIW. |
|
Ah OK so the problem is that the rootfs image is missing. @mgalka Could you please take a look? I think this might be related to the |
|
I believe it's not an infrastructure error but a limitation of how debos creates images, it has a fixed maximum size for the rootfs which can be configured so we might just need to add a parameter in |
|
From a user point of view it's infra - it's something I can't change (and something which started failing after I pushed the PR). @nuclearcat did mention making this configurable but I've no idea what the status is on that. |
|
Adding skip label because of #1994 |
These job templates allow the generation of LAVA test jobs for kvm-unit-tests using the existing LAVA integration in test-definitions. Signed-off-by: Mark Brown <[email protected]>
broonie
force-pushed
the
kvm-unit-tests
branch
from
83763e9 to
bc3b269
Compare
broonie
removed
the
staging-skip
These filesystems support running kvm-unit-tests using the latest LAVA test definitions. These can work with prebuilt tests in /opt/kvm-unit-tests so build the tests there and install a copy of qemu so that we can run them. Signed-off-by: Mark Brown <[email protected]>
Provide the base definition for kvm-unit-tests, allowing it to be enabled for boards. Signed-off-by: Mark Brown <[email protected]>
The Le Potato and Raspberry Pi 4 boards in my lab should have some capacity to run kvm-unit-tests. Signed-off-by: Mark Brown <[email protected]>
broonie
force-pushed
the
kvm-unit-tests
branch
from
bc3b269 to
278af87
Compare
|
Closing, as we are deprecating the legacy system. If this is still an issue or relevant, please re-open it under the Maestro system. Thank you for your contribution, and sorry for the inconvenience. |
The kvm-unit-tests provide low level coverage of KVM functionality, as the name suggests being very simple low level guests which exercise functionality in a much more focused fashion than running a full guest OS would.
This series depends on the very latest test definitions upstream, specifically Linaro/test-definitions@755466a - otherwise the only option is to build the testsuite at runtime.