Your message dated Tue, 09 Jan 2024 21:09:34 +0000 with message-id <e1rnjlq-009cwm...@fasolo.debian.org> and subject line Bug#1060340: fixed in neovim 0.9.5-3 has caused the Debian Bug report #1060340, regarding neovim/experimental FTBFS on most architectures: test hang 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.) -- 1060340: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1060340 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
--- Begin Message ---Source: neovim Version: 0.9.5-2 Severity: serious Tags: ftbfs https://buildd.debian.org/status/logs.php?pkg=neovim&ver=0.9.5-2 ... -------- Running tests from test/functional/shada/shada_spec.lua RUN T4160 ShaDa support code preserves `s` item size limit with unknown entries: 3.16 ms OK RUN T4161 ShaDa support code preserves `s` item size limit with instance history entries: 2.70 ms OK RUN T4162 ShaDa support code leaves .tmp.a in-place when there is error in original ShaDa: 1.03 ms OK RUN T4163 ShaDa support code does not leave .tmp.a in-place when there is error in original ShaDa, but writing with bang: 1.19 ms OK RUN T4164 ShaDa support code leaves .tmp.b in-place when there is error in original ShaDa and it has .tmp.a: 2.52 ms OK RUN T4165 ShaDa support code leaves .tmp.z in-place when there is error in original ShaDa and it has .tmp.a … .tmp.x: 2.07 ms OK RUN T4166 ShaDa support code errors out when there are .tmp.a … .tmp.z ShaDa files: 1.31 ms OK RUN T4167 ShaDa support code reads correctly various timestamps: 16.28 ms OK RUN T4168 ShaDa support code correctly uses shada-r option: 6.67 ms OK RUN T4169 ShaDa support code correctly ignores case with shada-r option: 3.22 ms OK RUN T4170 ShaDa support code is able to set &shada after &viminfo: 14.19 ms OK RUN T4171 ShaDa support code is able to set all& after setting &shada: 1.65 ms OK RUN T4172 ShaDa support code is able to set &shada after &viminfo using :set: 1.39 ms OK RUN T4173 ShaDa support code setting &shada gives proper error message on missing number: 3.12 ms OK RUN T4174 ShaDa support code does not crash when ShaDa file directory is not writable: 28.95 ms OK RUN T4175 ShaDa support code does not write NONE file: 28.85 ms OK RUN T4176 ShaDa support code does not read NONE file: 25.08 ms OK -- Tests exited non-zero: Process terminated due to timeout -- No output to stderr. CMake Error at /<<PKGBUILDDIR>>/cmake/RunTests.cmake:100 (message): functional tests failed with error: Process terminated due to timeout E: Build killed with signal TERM after 150 minutes of inactivity
--- End Message ---
--- Begin Message ---Source: neovim Source-Version: 0.9.5-3 Done: James McCoy <james...@debian.org> We believe that the bug you reported is fixed in the latest version of neovim, 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 1060...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. James McCoy <james...@debian.org> (supplier of updated neovim 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: Tue, 09 Jan 2024 15:42:25 -0500 Source: neovim Architecture: source Version: 0.9.5-3 Distribution: experimental Urgency: medium Maintainer: Debian Vim Maintainers <team+...@tracker.debian.org> Changed-By: James McCoy <james...@debian.org> Closes: 1060340 Changes: neovim (0.9.5-3) experimental; urgency=medium . * Remove lua-nvim Build-Depends * Provide a custom $XDG_RUNTIME_DIR when running tests. $XDG_RUNTIME_DIR is leaking into the sbuild environment on the buildds and causing the tests to hang because the test can't access the external directory. Thanks to Vincent Blut for diagnosing the problem. (Closes: #1060340) * Revert "Skip wundo_spec.lua tests since they hang on the buildds" Checksums-Sha1: 109a2b92fe35f26a83a0e2aa578c7ec91929f74c 2920 neovim_0.9.5-3.dsc ecd226ad295b6f88fd5b61d80a5a905d9a1ffd04 25396 neovim_0.9.5-3.debian.tar.xz Checksums-Sha256: 7956737acf206f52f11afa004d150587409ba916b94ff195dbe52796f13f570e 2920 neovim_0.9.5-3.dsc ce7d2b05b4497c9af536b471399b464f52be1f9d2bc3c94f9be54f361b4063bc 25396 neovim_0.9.5-3.debian.tar.xz Files: 40fa526f10e20d3628cf5cdcce2fbe67 2920 editors optional neovim_0.9.5-3.dsc aab63e52c49fe690e613d9aef3af34f9 25396 editors optional neovim_0.9.5-3.debian.tar.xz -----BEGIN PGP SIGNATURE----- iQKoBAEBCgCSFiEEkb+/TWlWvV33ty0j3+aRrjMbo9sFAmWdsVJfFIAAAAAALgAo aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldDkx QkZCRjRENjk1NkJENURGN0I3MkQyM0RGRTY5MUFFMzMxQkEzREIUHGphbWVzc2Fu QGRlYmlhbi5vcmcACgkQ3+aRrjMbo9sjMw//eVse23p9HzDEix3ELxq8oE+PgIAI /KG0xXuwKnuFgwc4zhRF37z9BAStyUWzmd5JQaq32MEPmR9tusy5ryhwJfsnpuXD yY/HG5/VwaXU14BHX2egSpcgD/cqAl7cdrsh2gDepCemyvTk7zoP4L6IiiJpSB6w psv0zWw/uzyoVWJOd5ZgApp8GHitiP5NQ3ZcerNQPI8U+TAJU/9XHON1Kgwi7KNP BYHXkCExu+CRSCzaAlEAObAHIvVvCiD5dtuUSotVS9eJvfDdSOdlVU82LahIWsGw sZtHuTvtP7+8EFF9dmHiBUdZ8wIpyqdfYNYJmwKxCNaj4+OUfs5Ip3itJ8FrFsHf 2dzKxsswu9Awl+oeExRG+KK+69a7AgU3lr7azHcVNtxe52BaU0yoHHjVNCZubc9m IWzT8YC1WtkOZOjMnzz3KV+eGipjQIOGrcVZ3WQVDE0o17N6WdmRTUV8Lhnhwb7i V1lXA+oU1VE7OR2KoxnwKGaycWKLSXZBiMgzkN0yHj12wvC+im6bd78gi43SEzE4 tXFQnbHRcxLVmdNhkZpkJX3TQiKiiucyacHPKkO4+h2GZYi0b3nbmbx+SK1Ymxb9 LiqbuB5RR4h3bDoL7pfYtOcugqiUWoqcfFmZ92GeArrQMyjl1L2XYZ/esVoV5VaJ zqtjUUhw6YO7j7Y= =rjAu -----END PGP SIGNATURE-----
--- End Message ---
