On Sun, 6 Nov 2022 07:30:38 +0100 Paul Gevers <elb...@debian.org> wrote:
> Dear maintainer(s),
Hello Paul
> I looked at the results of the autopkgtest of your package. I noticed
> that it regularly fails (after the fix for bug #1019221).
>
> Because the unstable-to-testing migration software now blocks on
> regressions in testing, flaky tests, i.e. tests that flip between
> passing and failing without changes to the list of installed packages,
> are causing people unrelated to your package to spend time on these
> tests.
>
> Don't hesitate to reach out if you need help and some more information
> from our infrastructure.
It's impossible for me to reproduce this locally, can you still see that
in the CI runs?
For me this looks like a race condition, the test code already waits for
2 sec after the start of the nut daemon an drivers to be certain that
everything is properly started. I can increase that sleep, but that's
probably not the best solution. An other solution is to have a loop
checking that the (dummy) driver is really connected, but I need to
investigate how and I've no time ATM.
Last solution could be to ask the release team to tag this bug as
"bookworm-ignore" so it can be part of the upcoming release and try to
fix this for the next one.
WDYT?
Kind regards,
Laurent Bigonville
