Hi,
On Thu, 27 Nov 2025 19:30:15 +0100 Hilko Bengen <[email protected]> wrote:
* Paul Gevers:
> Source: libguestfs
> Version: 1:1.54.1-3
> Severity: serious
> User: [email protected]
> Usertags: flaky
>
> Dear maintainer(s),
>
> I looked at the results of the autopkgtest of your package because it
> was showing up as a regression for binutils. In bug 1120436 I already
> mentioned the test appears to have become flaky. Today I scheduled 5
> tests on amd64/unstable, 5 retries of for binutils on arm64/testing
> and 5 tests on riscv64/testing. The failures were 3/0/3. The failures
> seem to be different on each architecture (at least the logs don't
> always end the same).
The autopkgtest failures rhyme with recent test failures during builds
that I have only been able to reproduce if KVM was not available,
causing qemu to fall back to its TCG backend.
Can you tell me whether KVM can be used in autopkgtests?
This is also affecting regular builds, at least on amd64, see [1]. This is
blocking the ongoing ocaml transition, can you take a look and hopefully provide
a quick solution? If those tests can't be run under qemu's TCG backend, and the
package can't control which backend is in use, then maybe those tests should be
disabled for the time being.
Cheers,
Emilio
[1] https://buildd.debian.org/status/logs.php?pkg=libguestfs&arch=amd64
