Your message dated Wed, 28 Oct 2026 20:45:03 +0000
with message-id <[email protected]>
and subject line Bug#1151416: fixed in wsjtx 3.3.0~beta2+dfsg-2
has caused the Debian Bug report #1151416,
regarding wsjtx FTBFS on riscv64: test_jtty_payload_correlators failure
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.)
--
1151416: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1151416
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Source: wsjtx
Version: 3.2.0~rc1+dfsg-2
Severity: serious
Tags: ftbfs
https://buildd.debian.org/status/logs.php?pkg=wsjtx&arch=riscv64
...
The following tests FAILED:
16 - test_wsjtx_startup (Timeout)
37 - test_configuration_radio (Timeout)
111 - test_decoder_engine_fst4 (Timeout)
115 - test_decoder_engine_fst4_omp (Timeout)
170 - test_jtty_continuous_decode (Timeout)
185 - test_jtty_payload_correlators (Failed)
Upstream recently started getting too strict about
test timeouts and I was looking into relaxing these,
but test_jtty_payload_correlators is an actual failure:
...
172/284 Test #185: test_jtty_payload_correlators
.....................................***Failed 0.04 sec
ERROR STOP shared M1 differs from separate original-order accumulation
Error termination. Backtrace:
#0 0x3fbea2a1b5 in ???
#1 0x3fbea2aa89 in ???
#2 0x3fbea2b7f5 in ???
#3 0x2ac473e579 in require
at tests/unit/jtty/test_jtty_payload_correlators.f90:105
#4 0x2ac473e579 in test_jtty_payload_correlators
at tests/unit/jtty/test_jtty_payload_correlators.f90:24
#5 0x2ac473cbf9 in main
at tests/unit/jtty/test_jtty_payload_correlators.f90:3
...
--- End Message ---
--- Begin Message ---
Source: wsjtx
Source-Version: 3.3.0~beta2+dfsg-2
Done: Christoph Berg <[email protected]>
We believe that the bug you reported is fixed in the latest version of
wsjtx, 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 [email protected],
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Christoph Berg <[email protected]> (supplier of updated wsjtx 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 [email protected])
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
Format: 1.8
Date: Wed, 28 Oct 2026 20:38:24 +0100
Source: wsjtx
Architecture: source
Version: 3.3.0~beta2+dfsg-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Hamradio Maintainers <[email protected]>
Changed-By: Christoph Berg <[email protected]>
Closes: 1151416
Changes:
wsjtx (3.3.0~beta2+dfsg-2) unstable; urgency=medium
.
* Ignore tests on riscv, it's slow and has problems. (Closes: #1151416)
Checksums-Sha1:
c8da4d472bea98d6872c0fe5c5cdec2d7eddbdfc 2526 wsjtx_3.3.0~beta2+dfsg-2.dsc
4f5b15b283cbdff50002d9c0e86ec1b90f4c50a7 20476
wsjtx_3.3.0~beta2+dfsg-2.debian.tar.xz
Checksums-Sha256:
bb8bade4182e44217d2e685c59a47bb130a16f18bda7a604456d075017d04327 2526
wsjtx_3.3.0~beta2+dfsg-2.dsc
fb601cd40880e236bf676f8d14dbe7ef9bb94c37f15425de09b0882c773bfa87 20476
wsjtx_3.3.0~beta2+dfsg-2.debian.tar.xz
Files:
28b3cf31b00813c3dad27c470be2e673 2526 hamradio optional
wsjtx_3.3.0~beta2+dfsg-2.dsc
6ffe5f690288cac621263c0b763d2f9c 20476 hamradio optional
wsjtx_3.3.0~beta2+dfsg-2.debian.tar.xz
-----BEGIN PGP SIGNATURE-----
iQIzBAEBCgAdFiEEXEj+YVf0kXlZcIfGTFprqxLSp64FAmriU9cACgkQTFprqxLS
p67X7A/+PfxmKdJysr0lp5X4Qre4XFsPmBVaK8n43bLoLHgQh8HZwvrld47zMi1P
AkX88u6ltBfV69XVLhr867HBU+JJw9I/r22Tao4Hp3kPZkE9Dx/he6/Zg25yrCS/
+sfAX5+GyxnRqtuPSogCwOdkliHt+MIoIjtE9/pRZUxyY4i7EBGoCdZtAI0izcmg
gLtjW7UTbNaaWBR0UJ01mppgdK/+HIsikSypKplnGYC5MY07+LvWf2S2bytpH5Wt
2xCm9FjhnqOBa7h6SWPr8isdMg9EIzTNNmKr7wwtwS595yLrrVVEySvxjAx76ikl
+vcsdqaXKGiL+rlmEwSJctYdl6LCLsT4EPZTSuuihflClDpsxGQpLOL9Qg/3VYTm
TI6vh3kw1ORkKou5ONOVsIJ/jnEwDTcJrM2Jw7QY2H5k+u6jnUiE0DyA+MnoiIGG
62BdFGIvkStYrF4INtq6ARaa99nBkKU2I4eLrzl+ZPry2QvGjW1KmyrpfVIAEK6I
l0IPg+LLFu9VVoBeIgEX9ngkBqF51AuEZzjgt3oWei/q8WVWMXhP3gr3wovG+jkY
758K5/ToPYJwHYYneiCiAi5oTLD9ttGBAtARqqr3A12rv7WzuCdWgYG6Mita4BcC
DB4tMPB/HfYkz54o/S86gkA6/hQQqOU8A165TSsBWn2WkmMlzhc=
=vY8+
-----END PGP SIGNATURE-----
pgpUFyy_ciUeb.pgp
Description: PGP signature
--- End Message ---
