Your message dated Thu, 06 Aug 2026 01:33:02 +0200
with message-id <[email protected]>
and subject line Re: Bug#1131809: dracut: ppc64el autopkgtest are flaky and
take 7 hours per run
has caused the Debian Bug report #1131809,
regarding dracut: ppc64el autopkgtest are flaky and take 7 hours per run
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
1131809: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1131809
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Source: dracut
Severity: serious
Justification: blocks other packages from migrating
Dear Maintainer(s),
The dracut autopkgtests on ppc64el are flaky, and many runs fail:
https://ci.debian.net/packages/d/dracut/testing/ppc64el/
What's worse is that each run is ~7 hours, so it takes a full day just
for a couple retries. This blocks other packages from migrating.
If this is not possible to fix, please consider disabling autopkgtest
on ppc64el, or marking the test suite as flaky. Thanks.
--- End Message ---
--- Begin Message ---
Version: 111-6
On Tue, 2026-08-04 at 18:31 +0800, Miao Wang wrote:
> Hi,
>
> > 2026年7月22日 06:51，Miao Wang <[email protected]> 写道：
> >
> > >
> > > 2026年7月22日 06:39，Benjamin Drung <[email protected]> 写道：
> > >
> > > On Thu, 2026-07-16 at 17:33 +0800, Miao Wang wrote:
> > > > On Tue, 30 Jun 2026 20:18:40 +0200 Paul Gevers <[email protected]>
> > > > wrote:
> > > > > Hi,
> > > > >
> > > > > On 29-06-2026 13:12, Benjamin Drung wrote:
> > > > > > > For now, I've added dracut/loong64 to the reject_list to save
> > > > > > > resources
> > > > > > > (the test get triggered often).
> > > > > >
> > > > > > The long execution time is caused by the individual tests running
> > > > > > into
> > > > > > the test-configured timeout. I just uploaded dracut 110-4 which
> > > > > > contains
> > > > > > a patch to use edk2 firmware for loong64 tests. This should resolve
> > > > > > running into the timeouts.
> > > > >
> > > > >
> > > > > I've scheduled a run manually. Let's see how it fares.
> > > >
> > > > Hi, I just noticed you have discussed the autopkgtest failures on
> > > > loong64
> > > > here. At first the failure was because the UEFI firmware was not used
> > > > and
> > > > the Linux kernel relies on the ACPI table provided by the UEFI firmware
> > > > to work correctly. Later the failure is because the race condition in
> > > > qemu.
> > > > I just sent patches to qemu to fix this [1].
> > >
> > > Thank you. Looking at the loong64 test logs [1] shows an execution time
> > > between found and eight hours. The test for 111-6 has this result:
> > >
> > > 16179s lsinitrd PASS (superficial)
> > > 16179s 10-basic PASS
> > > 16179s 13-sysroot PASS
> > > 16179s 14-hooks PASS
> > > 16179s 40-systemd PASS
> > > 16179s 42-systemd-initrd PASS
> > > 16179s 43-kernel-install PASS
> > > 16179s 80-getarg PASS
> > > 16179s 81-skipcpio PASS
> > > 16179s 11-usr-mount PASS
> > > 16179s 20-storage PASS
> > > 16179s 26-enc-raid-lvm PASS
> > > 16179s 21-overlayfs FAIL non-zero exit status 124
> > > 16179s 30-dmsquash FAIL non-zero exit status 1
> > > 16179s 31-livenet PASS
> > > 16179s 41-full-systemd PASS
> > > 16179s 44-drivers PASS
> > > 16179s 45-systemd-import PASS
> > > 16179s 46-systemd-sysext PASS
> > > 16179s 50-network PASS
> > > 16179s 60-nfs FAIL non-zero exit status 124
> > > 16179s 70-iscsi FAIL non-zero exit status 124
> > > 16179s 71-iscsi-multi PASS
> > > 16179s 72-nbd PASS
> > >
> > > 21-overlayfs and 30-dmsquash wich should be fixed by your qemu fix I
> > > assume.
> > >
> > > 60-nfs and 70-iscsi show multiple "PROGRESS CODE: V03040003 I0" lines,
> > > but I see no obvious lockup error message. Will those be fixed by your
> > > qemu fix as well or are they caused by a different issue?
> > >
> > > [1] https://ci.debian.net/packages/d/dracut/testing/loong64/
> > >
> >
> > The bug is actually a race condition in the internal CPU
> > state emulated by qemu related to interrupt handling, As a result,
> > the failure can happen randomly. In the log [1], I can see
> > lock up messages during 70-iscsi. Regarding 60-nfs, I can see the
> > direct reason for the failure is because of the unresponding
> > nfs server. I guess the actual reason might still be the same.
> > The lock up might happen on the vm served as nfs server.
> >
> > The message "PROGRESS CODE: " is printed by the firmware
> > during initialization, which is normal and can be ignored.
>
> As shown in the recent autopkgtest logs, the failure of dracut on loong64
> should have been fixed after the upload of qemu 11.0.3+ds-2.
Thanks. I'll mark this bug as fixed. In case new test failure appear,
please create new bug reports.
--
Benjamin Drung
Debian & Ubuntu Developer
--- End Message ---
