On Wed, 2024-11-20 at 12:57 +0000, Luca Boccassi wrote: > On Wed, 20 Nov 2024 at 12:55, Benjamin Drung <bdr...@debian.org> wrote: > > > > On Tue, 19 Nov 2024 11:39:01 +0000 Luca Boccassi <bl...@debian.org> > > wrote: > > > Source: dracut > > > Version: 105-1 > > > User: debian...@lists.debian.org > > > Usertags: flaky > > > Severity: grave > > > Justification: blocks other packages from migrating > > > > > > Dear Maintainer(s), > > > > > > The new autopkgtest added in 105-1 are all failing, so they block > > > other packages that get scheduled together in debci from migrating: > > > > > > https://ci.debian.net/packages/d/dracut/testing/arm64/ > > > > > > If this cannot be solved quickly, please consider adding 'flaky' to > > > the list of restrictions so that failures no longer halt migrations, > > > until the tests can be stabilized. Thanks. > > > > The tests need some (upstream) work to succeed on arm64. So these test > > should be marked as flaky. > > > > To summarize: The test currently only work on amd64, but require KVM > > support. On all other architectures more work is needed. > > > > Should I drop these architectures for now? > > Up to you, either that or marking explicitly as "flaky" would solve > the immediate issue, so either works for me. Thanks.
Can it be marked as "flaky" only via debian/test/control? Is there a way to mark it as flaky only on specific architectures? Can we disable QEMU support for the dracut autopkgtest? -- Benjamin Drung Debian & Ubuntu Developer
