Source: trapperkeeper-scheduler-clojure
Version: 1.1.3-7
Severity: important

Hi,

Your package has an autopkgtest, great. However, I noticed that it very often (on some architectures) times out after 2:47 hours. Because the test is marked flaky, it doesn't lead to a false failure, but it does put a bit of unwanted stress on the infrastructure, as a successful run only costs 3 to 4 minutes. Can you please either prevent the test from hanging, or just drop the test? Tests marked as flaky are only useful if humans regularly inspect them, but eg on i386 in testing [1], the problem is visible for 1.5 years now.

Paul

https://ci.debian.net/packages/t/trapperkeeper-scheduler-clojure/testing/i386/

-- System Information:
Debian Release: trixie/sid
  APT prefers testing
  APT policy: (990, 'testing')
Architecture: amd64 (x86_64)

Kernel: Linux 6.10.6-amd64 (SMP w/4 CPU threads; PREEMPT)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Attachment: OpenPGP_signature.asc
Description: OpenPGP digital signature

Reply via email to