Dear maintainer(s),

Your package has an autopkgtest, great. However, the last run(s) in
testing on amd64 failed [1]. Can you please investigate the situation
and fix it?

The release team has announced [2] that failing autopkgtest on amd64 and
arm64 are considered RC in testing.

If you believe the failure is related to the infrastructure rather than
the test of the package, don't hesitate to reach out to the ci-team on
IRC (#debci on oftc) or via debian-ci@lists.debian.org.

Paul

PS: this bug submission was largely automated, please contact me if you
think I should improve my workflow.

[1] https://ci.debian.net/packages/b/bash-completion/testing/amd64
[2] https://lists.debian.org/debian-devel-announce/2019/07/msg00002.html

https://ci.debian.net/packages/b/bash-completion/testing/amd64/65404283/

1018s =================================== FAILURES
===================================
1018s ______________________ TestUnitCompgenFiledir.test_26[f]

We believe that the bug you reported is fixed in the latest version of
bash-completion, 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 1119845@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Gabriel F. T. Gomes <gabriel@debian.org> (supplier of updated bash-completion 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: Sun, 02 Nov 2025 20:24:00 -0800
Source: bash-completion
Architecture: source
Version: 1:2.16.0-8
Distribution: unstable
Urgency: medium
Maintainer: Gabriel F. T. Gomes <gabriel@debian.org>
Changed-By: Gabriel F. T. Gomes <gabriel@debian.org>
Closes: 1119845
Changes:
 bash-completion (1:2.16.0-8) unstable; urgency=medium
 .
   * Backport workaround for bug in bash 5.3 (Closes: #1119845).
Checksums-Sha1:
 4eb67114f2bf0af2e0632431841ad0c1bbce58bf 2088 bash-completion_2.16.0-8.dsc
 162ffa7b2b005a0c356c96a82fab10788a86ef74 20908 bash-completion_2.16.0-8.debian.tar.xz
 b9ff6e4923f39402c1c7674604a95b67d1e5b2d7 5598 bash-completion_2.16.0-8_amd64.buildinfo
Checksums-Sha256:
 8cf7d0333119e28717d02007ed0c50e15e9366756c4bfa9119939a4167619dfb 2088 bash-completion_2.16.0-8.dsc
 e68ef1f7d9cf4b2dce85cf5139a8d515d0baa65b41152f053806c636ba6b87da 20908 bash-completion_2.16.0-8.debian.tar.xz
 e1f8168ad1bf5b53bf6445fc254f92a54cd5569ae3df55c98a8f792ab2188e7a 5598 bash-completion_2.16.0-8_amd64.buildinfo
Files:
 f76c0bd0f3940fb5f91db1d1f820a29b 2088 shells standard bash-completion_2.16.0-8.dsc
 5e9462b64b24cfeaa084eec097fdf150 20908 shells standard bash-completion_2.16.0-8.debian.tar.xz
 892bd557517719b8378a3e61590d793c 5598 shells standard bash-completion_2.16.0-8_amd64.buildinfo
-----BEGIN PGP SIGNATURE-----

iQJHBAEBCgAxFiEE+wUJHFVUA1wadvc8rpsRODhuyvIFAmkIP5ATHGdhYnJpZWxA
ZGViaWFuLm9yZwAKCRCumxE4OG7K8jswD/4lEFB6TrPkuAFcpoJpxb9myWPu0avV
RBatI0na8RydW3289ye/BVAjYhqYShMYfrch2BQ8DZQy74JOL4ujf1BeIr2BDchF
+GUdgV+kJvG96ImN71yaVcrk8MeCud2viFZbhLqvUf7pK68IrtnifJVxh5EyyO36
IgQLY3+NaitvRoL07WTxSwMrD8ThsNfLNnspSht7hflhWF1bqvHfFsMjZnb63PxW
smq4VZuh8Df55RhoTKTM+PC6DbX7GrIDg1U/xFk/ny+2HSypl3/5QqHifHI545s5
Qp62OyZTNh+fX7FD1yEDja8l4fr18d+DSEEEYhK5eOvQ+ISEVueg09zZ+yUSxFVL
5hO10S5hK+1fPk+b39TYuqIa7D7g+s5cfMoJ3eVcCUTfilQwPf48Ycv1D99/8SOn
+kjJKjsutMtbstH4ZzVtGnm6B+5VH6QYHmmAuO3WXfQPA2HmDpyF9iD68/dS+bUO
0IBVc1Szm4M4vNLIpVYj266BAizvfqwRqCj/7ynQ8e/AU161KOuhUzJVU92WFsV4
pzaW9Gm9dFQ7OkQnjLjKlgx8YHNMb+7JmSegdHyQeLj6SjNccUNxAK+0cExukfOF
ymOrjfuGd4EyCQJPkmkWggRDd7zGpNd6BUxJzbzBaE4utoWo1Cg12PQaepLf4p0a
zWqg0OqeREe6Sg==
=qXf6
-----END PGP SIGNATURE-----

Thanks, Paul.

I'm investigating the issue. It is not a problem with the autopkgtest infrastructure. I succesfully reproduced it on unstable.

Reopening because there are several other autopkgtest tests failing
now, even though the one reported by Paul is fixed.

(full report at https://ci.debian.net/packages/b/bash-completion/unstable/amd64/65748285/)

1402s =========================== short test summary info ============================
1402s FAILED test/t/test_ip.py::TestIp::test_netconf - AssertionError: assert 'show...
1402s FAILED test/t/unit/test_unit_compgen.py::TestUtilCompgen::test_7_xcmd - pexpe...
1402s ERROR test/t/test_complete.py::TestComplete::test_2 - pexpect.exceptions.TIME...
1402s ERROR test/t/test_export.py::TestExport::test_8 - pexpect.exceptions.TIMEOUT:...
1402s ERROR test/t/test_export.py::TestExport::test_no_equals_sign_for_function - AssertionError: Error running "_comp__test_export_f_canary() { return; }": exit status=2, output="
1402s ERROR test/t/test_ip.py::TestIp::test_monitor - pexpect.exceptions.TIMEOUT: T...
1402s ERROR test/t/test_jq.py::TestJq::test_no_completion_after_args - pexpect.exce...
1402s ERROR test/t/test_locale_gen.py::TestLocaleGen::test_1 - pexpect.exceptions.T...
1402s ERROR test/t/test_mii_tool.py::TestMiiTool::test_2 - pexpect.exceptions.TIMEO...
1402s ERROR test/t/test_ngrep.py::TestNgrep::test_2 - pexpect.exceptions.TIMEOUT: T...
1402s ERROR test/t/test_tracepath.py::TestTracepath::test_1 - pexpect.exceptions.TI...
1402s = 2 failed, 1608 passed, 466 skipped, 17 xfailed, 7 xpassed, 9 errors in 1369.90s (0:22:49) =
1402s autopkgtest [10:54:11]: test upstream: -----------------------]

Is it possible that these CI test timeouts might be fixed by [1e24598]?

This commit is included in upstream [release 2.17] of 31 Oct 2025, which
does not seem to include any breaking changes. Therefore, perhaps 2.17
could land in unstable/testing and the CI might pass?

Upstream also released [2.18] on 5 July 2026, which has some larger
changes -- perhaps better for experimental?



Sources:

[1e24598]:
https://github.com/scop/bash-completion/commit/1e2459827e9b3b03a95f244349472a89142e2ae2

[release 2.17]: https://github.com/scop/bash-completion/releases/tag/2.17.0

[2.18]: https://github.com/scop/bash-completion/releases/tag/2.18.0

I built 2.17 locally and ran the test suite a couple of times, and,
though the test suite runs much faster, it did not fix the TIMEOUT
errors (though every now and then the test suite ran without any errors).

A MR was created upstream [MR] that, I think, works around the issue in
a more sustainable way, by doing a retry of the failing part of the test
in case of a TIMEOUT. This leaves tests that fail for other reasons
unaffected. It is not a complete fix, but I ran the test suite with this
in place a couple of times, and the test suite did no longer error out
(I ran it with a debug line so that I could see if the retry fired,
which it did).

Let's see if it gets accepted upstream.


[MR]: https://github.com/scop/bash-completion/pull/1722

 > ...> [MR]: https://github.com/scop/bash-completion/pull/1722

This MR was merged today.

Not sure if you want to wait for a new release, or backport the fix
until then?

Nice. Thanks for working on this.