Dear maintainer(s),

Your package has an autopkgtest, great. However, it fails on s390x.
What's worse, it fails because it seems to hang and eventually times out
due to autopkgtest. Can you please investigate the situation and fix it?
I copied some of the output at the bottom of this report.

The release team has announced [1] that failing autopkgtest on amd64 and
arm64 are considered RC in testing. Also tests that time out (while
normally running in much less time) are bad for our infrastructure. I
have added your package to our reject_list and will remove it once this
bug is closed.

More information about this bug and the reason for filing it can be
found on
https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation

Paul

[1] https://lists.debian.org/debian-devel-announce/2019/07/msg00002.html

https://ci.debian.net/packages/a/asterisk-espeak/testing/s390x/74209876/

100s autopkgtest [07:37:06]: test module-loadable: [-----------------------
101s Asterisk 22.10.1+dfsg+~cs6.17.60671434-1, Copyright (C) 1999 -
2025, Sangoma Technologies Corporation and others.
101s Created by Mark Spencer <markster@digium.com>
101s Asterisk comes with ABSOLUTELY NO WARRANTY; type 'core show
warranty' for details.
101s This is free software, with components licensed under the GNU
General Public
101s License version 2 and other licenses; you are welcome to
redistribute it under
101s certain conditions. Type 'core show license' for details.
101s
=========================================================================
10102s autopkgtest [10:23:48]: test module-loadable:
-----------------------]

Quoting Paul Gevers (2026-08-11 22:12:40)
closing this as not an issue with the package.

That fits my view of the situation: Nothing has changed in the package
and no compile-time warnings or errors have been noticed that caused
this change of behavior.

If you disagree then please reopen, but also I would then appreciate
suggestions as to how such an issue might be differently solved. E.g.
would you find it better that this package hardcodes that autopkgtest
should be skipped for the failing port, or to request ftpmasters drop
the package on the port with spuriously hanging autopkgtest?

Kind regards,

 - Jonas

Hi Jonas,


I'd expect you to think that a hang is something to worry about on an
official supported architecture. But I guess I was wrong.


Something changed between 2025-10-20 23:12:59 UTC and 2025-12-06
05:19:56 UTC. Unfortunately the logs have been recycled, so we can't see
what the failure was before 2025-10-20 23:12:59 UTC. I'll note that this
aligns with a similar change in src:asterisk, which also started to time
out, between 2025-10-15 09:11:40 UTC (PASS) and 2025-10-29 14:44:56 UTC.


I agree that having it at serious was a bit exaggerated, sorry for that.
But I think it's a bug nevertheless, so I don't understand why you close
it without any resolution.


I don't understand why you call it spurious, could you elaborate? I'd
expect an alternative could be to fix the underlying issue? The s390x
porters are quite responsive if you need help with s390x specific knowledge.

Paul