Source: gscan2pdf
Version: 2.12.6-1
Severity: serious
User: debian...@lists.debian.org
Usertags: flaky

Dear maintainer(s),

I looked at the results of the autopkgtest of you package on s390x because it was showing up on our alert page [1]. I noticed that there were several runs that took 27h before timing out, while successful runs only take about 15 to 20 minutes. This is not limited to s390x, also other architectures fail regularly. In stable, the test also fails once in a while, but I didn't spot the timeouts there.

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.

On top of that, when a test just hangs that's not good for our infrastructure. I'll put gscan2pdf on our reject_list for amd64, armhf, i386, and s390x.

Don't hesitate to reach out if you need help and some more information
from our infrastructure.

Paul

[1] https://ci.debian.net/status/alerts/

Examples of 27h time out
https://ci.debian.net/data/autopkgtest/unstable/amd64/g/gscan2pdf/21000327/log.gz
https://ci.debian.net/data/autopkgtest/testing/armhf/g/gscan2pdf/22210007/log.gz
https://ci.debian.net/data/autopkgtest/unstable/i386/g/gscan2pdf/21000345/log.gz
https://ci.debian.net/data/autopkgtest/testing/s390x/g/gscan2pdf/22222205/log.gz

Attachment: OpenPGP_signature
Description: OpenPGP digital signature

Reply via email to