Your message dated Sun, 28 Sep 2025 22:20:46 +0300
with message-id <aNmKjn2y4WULnGqv@localhost>
and subject line Re: Bug#1112587: jenkins-job-builder: flaky autopkgtest on
amd64: parallelism issue?
has caused the Debian Bug report #1112587,
regarding jenkins-job-builder: flaky autopkgtest on amd64: parallelism issue?
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.)
--
1112587: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1112587
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Source: jenkins-job-builder
Version: 3.11.0-6
Severity: serious
User: [email protected]
Usertags: flaky
Control: found -1 3.11.0-7
Dear maintainer(s),
I looked at the results of the autopkgtest of your package because it
showed up as a regression for the p-u of jinja2. I noticed that it fails
very often on amd64 (and hardly on other architectures where I checked).
I saw the title of bug 1109968 and wondered if there's a parallelism
issue, our amd64 host has 64 cores and 256 GB RAM.
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.
Paul
OpenPGP_signature.asc
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Version: 6.4.2-1
On Sun, Aug 31, 2025 at 09:46:38AM +0200, Paul Gevers wrote:
> Source: jenkins-job-builder
> Version: 3.11.0-6
> Severity: serious
> User: [email protected]
> Usertags: flaky
> Control: found -1 3.11.0-7
>
> Dear maintainer(s),
>
> I looked at the results of the autopkgtest of your package because it showed
> up as a regression for the p-u of jinja2. I noticed that it fails very often
> on amd64 (and hardly on other architectures where I checked). I saw the
> title of bug 1109968 and wondered if there's a parallelism issue, our amd64
> host has 64 cores and 256 GB RAM.
>...
This issue is already fixed in trixie:
jenkins-job-builder (6.4.2-1) unstable; urgency=medium
...
* Remove autopkgtest that must be rewritten (TODO).
-- Thomas Goirand <[email protected]> Tue, 17 Dec 2024 09:07:33 +0100
The autopkgtest now fails always, and this seems to be due to the second
issue fixed by the MR from #1109968.
Thomas, could you make an upload with the MR,
unless you have some objection to that?
> Paul
cu
Adrian
--- End Message ---
