On Sat, 24 Aug 2024 at 21:25:03 +0200, Paul Gevers wrote: > On 24-08-2024 20:53, Guilhem Moulin wrote: >> Awesome, thanks! Right now these tests have “Architecture: amd64 i386”, >> is the runner able to run i386 too or should I remove it from the list? > > Tests with isolation-machine will only run on amd64, no need to special case > them further. If there are tests that you expect to only work on qemu that > are NOT yet tagged with isolation-machine should be marked as such.
I think we misunderstood each other. We indeed have isolation-machine tests and it's great if they now can be run on debci infrastructure, but this bug is about the cryptroot-* series which can run on lxc or schroot. These tests themselves start qemu and bootstrap a guest to test unlocking at early boot stage. We chatted about it during DebConf21 and I believe it's not possible to rely on debci's own QEMU setup for such tests. AFAICT the issue with #-1 is that we can't control which runner we'll end up running on, and tests appear to be flaky on non-KVM capable runners. https://salsa.debian.org/ci-team/debci/-/issues/166 is not closed yet, so I guess cryptroot-* will have to remain flaky for now. But it's great if the isolation-machine tests can run on debci infrastructure :-) -- Guilhem.
signature.asc
Description: PGP signature
