On 28/05/2024 10.16, Johannes Schauer Marin Rodrigues wrote:
But I wonder, the autopkgtest results now say (for example for arm64):
657s I: Summary:
657s I: PASS ezurio-qcacld-2.0/0.0~git20230623.2cd31b6 6.7.12-arm64
657s I: SKIP ezurio-qcacld-2.0/0.0~git20230623.2cd31b6 6.7.12-cloud-arm64
657s I: PASS ezurio-qcacld-2.0/0.0~git20230623.2cd31b6 6.7.12-rt-arm64
As a result, the whole test is marked as "skipped" and not "successful", so I
No. The neutral state comes from autopkgtest-pkg-dkms being
"superficial". As this only tests building the module but not its
functionality, this is only some kind of smoketest and thus has to be
marked "superficial". It is now possible to have "isolation-machine"
tests that could test module functionality (see e.g. dm-writeboost-dkms)
but not if this requires special hardware.
So there is probably no migration boost possible for most -dkms
packages. But at least we should be able to catch build failures on new
kernels earlier. (But that will need some work on britney as a new
kernel upload does not yet trigger all -dkms packages.)
Andreas
