Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.debian.kernel > #91792 > unrolled thread

Bug#1131809: dracut: ppc64el autopkgtest are flaky and take 7 hours per run

Back to article view | Back to linux.debian.kernel

Contents

  Bug#1131809: dracut: ppc64el autopkgtest are flaky and take 7 hours per run Luca Boccassi <bluca@debian.org> - 2026-03-24 23:00 +0100
    Bug#1131809: dracut: ppc64el autopkgtest are flaky and take 7 hours per run Benjamin Drung <bdrung@debian.org> - 2026-03-27 23:10 +0100
    Bug#1131809: dracut: ppc64el autopkgtest are flaky and take 7 hours per run Benjamin Drung <bdrung@debian.org> - 2026-06-29 13:20 +0200
    Bug#1131809: dracut: ppc64el autopkgtest are flaky and take 7  hours per run Miao Wang <shankerwangmiao@gmail.com> - 2026-07-16 11:40 +0200
    Bug#1131809: marked as done (dracut: ppc64el autopkgtest are  flaky and take 7 hours per run) "Debian Bug Tracking System" <owner@bugs.debian.org> - 2026-08-06 01:40 +0200

#91792 — Bug#1131809: dracut: ppc64el autopkgtest are flaky and take 7 hours per run

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.

[toc] | [next] | [standalone]

#91814

Hi,

On Tue, 2026-03-24 at 21:51 +0000, Luca Boccassi wrote:
> 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.

I spent a lot of time to address the flakyness of the dracut tests
(races, timeouts, etc). The flakyness should be fixed in dracut 110-7
(there is one more timeout fix for test 41 in 110-8).

There are three test failures of 110-7:

1) 72-nbd: kernel BUG at arch/powerpc/include/asm/interrupt.h:355
2) 70-iscsi: I/O error, dev sdb, sector 69122 op 0x0:(READ)
3) 71-iscsi-multi: timed out (last log line: "Run /init as init process")

So failure 1 and 2 look like kernel related. Failure 3 does not look
like dracut being the culprit.

-- 
Benjamin Drung
Debian & Ubuntu Developer

[toc] | [prev] | [next] | [standalone]

#93148

On Sat, 2026-06-27 at 11:58 +0200, Paul Gevers wrote:
> Hi,
> 
> I just had a look at the loong64 results. I didn't spot a successful run 
> yet, while most run for more than 8 hours and run into the global 
> autopkgtest timeout of 100000 seconds.
> 
> 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.

-- 
Benjamin Drung
Debian & Ubuntu Developer

[toc] | [prev] | [next] | [standalone]

#93356 — Bug#1131809: dracut: ppc64el autopkgtest are flaky and take 7 hours per run

On Tue, 30 Jun 2026 20:18:40 +0200 Paul Gevers <elbrus@debian.org> 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].

Cheers,

Miao Wang

[1]: https://lore.kernel.org/qemu-devel/20260716-loong-race-v2-1-01e68e4b850f@gmail.com/

[toc] | [prev] | [next] | [standalone]

#93616 — Bug#1131809: marked as done (dracut: ppc64el autopkgtest are flaky and take 7 hours per run)

[Multipart message — attachments visible in raw view] — view raw

Your message dated Thu, 06 Aug 2026 01:33:02 +0200
with message-id <1597ed36ef55f85fe1d2269d8145958e50afaeac.camel@debian.org>
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 owner@bugs.debian.org
immediately.)


-- 
1131809: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1131809
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems

[toc] | [prev] | [standalone]

Back to top | Article view | linux.debian.kernel

csiph-web