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/

We believe that the bug you reported is fixed in the latest version of
trapperkeeper-scheduler-clojure, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 1079807@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Jérôme Charaoui <jerome@riseup.net> (supplier of updated trapperkeeper-scheduler-clojure package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmaster@ftp-master.debian.org)
Format: 1.8
Date: Thu, 10 Sep 2026 00:58:54 -0400
Source: trapperkeeper-scheduler-clojure
Architecture: source
Version: 1.4.1-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Clojure Maintainers <team+clojure@tracker.debian.org>
Changed-By: Jérôme Charaoui <jerome@riseup.net>
Closes: 1047650 1079807
Changes:
 trapperkeeper-scheduler-clojure (1.4.1-1) unstable; urgency=medium
 .
   * New upstream version 1.4.1
   * switch to new upstream openvoxproject
   * switch packaging to dh-clojure (Closes: #1047650)
   * d/patches: add patch to print test case names
   * d/tests: switch to cognitect.test-runner
   * d/tests: kill unit tests after 1h
   * d/tests: only run unit tests on amd64 and arm64 (Closes: #1079807)
   * d/watch: update to v5 format and new upstream
   * Remove redundant Priority: optional from source stanza.
   * Update standards version to 4.7.4, no changes needed.
   * Removed Rules-Requires-Root
Checksums-Sha1:
 8bb28975a848d92f3ef7c17f63f48f49523cfe50 1877 trapperkeeper-scheduler-clojure_1.4.1-1.dsc
 d5c309c6269a6d94f328988cb326d5f055cdb43b 17756 trapperkeeper-scheduler-clojure_1.4.1.orig.tar.gz
 77a3df67c8d429dcec64200d8091f77be65c3fea 3876 trapperkeeper-scheduler-clojure_1.4.1-1.debian.tar.xz
 46075b2b15688e39d13df3c60c382a73069f06fb 11266 trapperkeeper-scheduler-clojure_1.4.1-1_amd64.buildinfo
Checksums-Sha256:
 7521f5306958b262beff699f91e893cbbce0981c3dfbed386b8c38a53dcdc86c 1877 trapperkeeper-scheduler-clojure_1.4.1-1.dsc
 10af86ac98c4566a129edba2abeb2250ded483adf87ddd0958186ac9b2cf8ba4 17756 trapperkeeper-scheduler-clojure_1.4.1.orig.tar.gz
 cb651c0b973f28cf181cc26a87713bfff6225f42db25a6b80b7a1887589ea6a6 3876 trapperkeeper-scheduler-clojure_1.4.1-1.debian.tar.xz
 6c97631f271271437f3c181baf85db4131b954d1348aa4aedbbd7be28ac5cf1b 11266 trapperkeeper-scheduler-clojure_1.4.1-1_amd64.buildinfo
Files:
 0f4617d8ac8c5c22c981b661c1a88dab 1877 java optional trapperkeeper-scheduler-clojure_1.4.1-1.dsc
 28f42968e1b5c245c1b6863adcc4155d 17756 java optional trapperkeeper-scheduler-clojure_1.4.1.orig.tar.gz
 bbbc3eef6aeffcdbe878164fcbe76c53 3876 java optional trapperkeeper-scheduler-clojure_1.4.1-1.debian.tar.xz
 5a6021a8aa9c15e05dbf364ef1e50455 11266 java optional trapperkeeper-scheduler-clojure_1.4.1-1_amd64.buildinfo
-----BEGIN PGP SIGNATURE-----

iHUEARYKAB0WIQTAq04Rv2xblqv/eu5pxS9ljpiFQgUCaqI7wwAKCRBpxS9ljpiF
QhMMAP0YBjyeTo5yOrqa9ZlDc2Du3gferInkmHQtmHP96JKXzQD/c/OJxnFEvMP0
wEtFwNlSPbrQbuoiFeEfAN6h7sowIww=
=iEG+
-----END PGP SIGNATURE-----

Hi,

I hope there's more to fix this bug than just that. Recently the package
hang twice on amd64:
2026-08-29 10:32:32 UTC (testing)
2026-08-10 11:41:04 UTC (testing)

Paul