Your message dated Wed, 12 Feb 2025 19:34:08 +0000 with message-id <e1tiiuq-00ab3n...@fasolo.debian.org> and subject line Bug#1093275: fixed in autopkgtest 5.44 has caused the Debian Bug report #1093275, regarding autopkgtest: flaky autopkgtest on riscv64: tests involving timeouts often fail 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 ow...@bugs.debian.org immediately.) -- 1093275: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1093275 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
--- Begin Message ---Source: autopkgtest Version: 5.42 Severity: serious User: debian...@lists.debian.org Usertags: flaky X-Debbugs-Cc: debian...@lists.debian.org autopkgtest has several tests that attempt to set a timeout such that the copy of autopkgtest under test will fail, by timing out at a specified point in the build (ideally while the test is still running sleep(1)). Unfortunately, the riscv64 workers on ci.debian.net are sufficiently slow that they often fail these tests "too soon", timing out before autopkgtest has reached the part of the test that we have made artificially slow; and as a result it fails "in the wrong way" and the overall test fails. We could in principle address this by making the arbitrary timeouts very long, and extending the sleep(1) to match, but that would make running the test suite even slower, even on fast architectures. It is already painfully slow for development (reasonably complete test coverage on my laptop takes 3½ hours, #1020699) so I don't really want to do this. Because this is all architecture-independent code, I think it would be sufficient test coverage if we only run these test-cases on "fast" architectures (x86 and maybe arm64), and skip them elsewhere. smcv
--- End Message ---
--- Begin Message ---Source: autopkgtest Source-Version: 5.44 Done: Simon McVittie <s...@debian.org> We believe that the bug you reported is fixed in the latest version of autopkgtest, 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 1093...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Simon McVittie <s...@debian.org> (supplier of updated autopkgtest 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 ftpmas...@ftp-master.debian.org) -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 Format: 1.8 Date: Wed, 12 Feb 2025 14:47:41 +0000 Source: autopkgtest Architecture: source Version: 5.44 Distribution: unstable Urgency: medium Maintainer: Debian CI team <team...@tracker.debian.org> Changed-By: Simon McVittie <s...@debian.org> Closes: 1052119 1078205 1093161 1093275 1093546 1094634 Changes: autopkgtest (5.44) unstable; urgency=medium . [ Simon McVittie ] * tests: Normally only test timeouts on known-fast architectures. We cannot make these test-cases reliable on slower machines like riscv64 without making the test suite take a long time even on faster machines. (Closes: #1093275) * virt-podman: Don't crash if the selected image has no labels (Closes: #1093546) * virt-podman(1): Mention how to generate images locally * build-podman(1): Consistently use podman in examples * virt-podman(1): Document that full systemd functionality needs CAP_SYS_ADMIN, how to obtain it, and the security considerations that mean it is not the default (Closes: #1078205) * d/control: Remove obsolete alternative dependency on pep8 (Closes: #1093161) * d/README.source: Mention some apt features that we cannot use yet * build-docker(1): Clarify the relationship between --tarball and --image. In particular clarify the circumstances under which a base image for use inside the container environment will be downloaded from a third-party container registry. . [ Paride Legovini ] * Turn test dependencies from package under test into strictly versioned dependencies (Closes: #1052119) * d/t/schroot: use eatmydata in the test schroot to speed up testing * autopkgtest(1): clarify usage of virt servers, suggest qemu * virt-schroot(1): add warning regarding lack of isolation . [ Ural Tunaboyu ] * buildvm-ubuntu-cloud: Don't exclude documentation . [ Jochen Sprickerhof ] * Add test dependency on apt to make it reproducible * virt-unshare: Keep apt lists when bootstrapping . [ Florent 'Skia' Jacquet ] * buildvm-ubuntu-cloud: Use server image for riscv64 testbeds, since no minimal image is available . [ Ian Jackson ] * virt-*: Exit with an error if stdin is in non-blocking mode * virt-*: Exit on EOF (Closes: #1094634) * virt-*: Warn on (invalid) leading whitespace in the virtualization protocol * virt-*: Reject empty commands Checksums-Sha1: 4ad713e8c10d05df83019d57678eda2fa730c593 2595 autopkgtest_5.44.dsc 4c7edd810aa888547c027fb8145a20550f6a4595 247632 autopkgtest_5.44.tar.xz 564b8f975b0ae1d79a25c099f762079ce7b4cf5d 6453 autopkgtest_5.44_source.buildinfo Checksums-Sha256: 6c1eb27c6b5eafb5cd69c36cecb66798359673358b23dad68ca5defb5e9577c2 2595 autopkgtest_5.44.dsc 5d66cad7e0e69dd7156f3560a7e24b68c298e03bc2caa9ef6708f5ef76f26ead 247632 autopkgtest_5.44.tar.xz 14106cba334355b659dd2db26847d59164ed9bd53530b77b0d50d070e72d5878 6453 autopkgtest_5.44_source.buildinfo Files: 6cb9d94921bfcb83304111af7325f049 2595 devel optional autopkgtest_5.44.dsc c3e76328780d95af6abeddb071306ae1 247632 devel optional autopkgtest_5.44.tar.xz 7e2daad6ffdd366edd1fa8a993b225ef 6453 devel optional autopkgtest_5.44_source.buildinfo -----BEGIN PGP SIGNATURE----- iQIzBAEBCgAdFiEEegc60a5pT6Jb/2LlI1wJnT6zMHYFAmes9p0ACgkQI1wJnT6z MHbmvhAAvGNIWK2YdbxivV/vyHxHnydYByjCnVgPyU+F3kQlgXGVW4jHqCtrRXn9 Co8zATn7BqFBkmAhAMSPPGEb5s+Y2l0E4LfWOMhPdEumCj0Wixf802NtJ03iWCr0 YGTWmm87Q45U5wpLkSbV2bpYawdbb20NHzRW8yZBFn8TthI2wSiy5OaodulQZx2a ZNnNrYekjAjsaDm01vIfwE3zparAbj2yOpZAnbOV0XIQB3a/vU9GZVAjh+o2o4E2 FQT7SUltLXNzf3K/7jXpLNP6Vr4PYxW/LZ7UNVswyf1vc6JSbUE7BBvAF4TYGAp4 U0bS708KZWZtvIOx8NemxMnPa2CeDRRS4fhkSHWLMG30ZszS+9KvxF5wL/mrwtLn 5YR9ePMl+fOpSRx2H6Gk5llSY+dXlqkTvEPpszcb5j+EcOQ+G69RXx6qICb1ANl2 yNsEJn6YVwWEcDvP5CKHH4ynvZ6bF6e9TerZyKmYUaroN6I5G0hrhmo3q0BCy+92 DMh8X3gpU5tWj/EAcf08AzHjvJPgfOXP/xbI453oSQ0sF9lOCXbl7gG0q+82iNxV Qvq57vR2wO0Qv6+JBR5o6Bptnq5R71J9nFVh8I9A2ntrLxuROex4ugLMJVtRzVIW GETepvg+ckKH3p5CVfPB4gvaazD2Ijc86xS2i1iM2hrVMtU2IG0= =om/g -----END PGP SIGNATURE-----
pgp02L0j9KSNZ.pgp
Description: PGP signature
--- End Message ---
