#1094069 rsyslog: FTBFS: dh_auto_test: error: make -j8 check "TESTSUITEFLAGS=-j8 --verbose" VERBOSE=1 returned exit code 2 #1094069
- Package:
- src:rsyslog
- Source:
- src:rsyslog
- Submitter:
- Lucas Nussbaum
- Date:
- 2025-11-19 20:41:01 UTC
- Severity:
- normal
- Tags:
Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): The full build log is available from: http://qa-logs.debian.net/2025/01/24/rsyslog_8.2412.0-1_unstable.log All bugs filed during this archive rebuild are listed at: https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20250124;users=lucas@debian.org or: https://udd.debian.org/bugs/?release=na&merged=ign&fnewerval=7&flastmodval=7&fusertag=only&fusertagtag=ftbfs-20250124&fusertaguser=lucas@debian.org&allbugs=1&cseverity=1&ctags=1&caffected=1#results A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! If you reassign this bug to another package, please mark it as 'affects'-ing this package. See https://www.debian.org/Bugs/server-control#affects If you fail to reproduce this, please provide a build log and diff it with mine so that we can identify if something relevant changed in the meantime.
Hi Lucas Am 24.01.25 um 21:23 schrieb Lucas Nussbaum: .. I tried to reproduce the build failure / test suite failure locally, but failed so far. The package itself also build rather reliably on the buildds: https://buildd.debian.org/status/logs.php?pkg=rsyslog&arch=amd64 Can you reproduce the failure in omfwd-lb-1target-retry-1_byte_buf.sh ? Regards, Michael
Hi. I guess he does, because usually when Lucas reports something it's because he already tried several times. In this case, in addition to Lucas getting build failures on machines with 8 CPUs, I'm also getting build failures (100% of the time) on machines with 1 CPU. Usually GRUB_CMDLINE_LINUX="nr_cpus=1" is enough to reproduce this, but if that does not work please contact me privately and I will gladly offer a VM to reproduce. Thanks.
Hi Michael, As Santiago said, I retry builds before filing bugs. I double-checked, and yes it failed twice. However, I tried it again and now I can't reproduce it. So there's probably something random/specific about the environment. I'm fine with downgrading the severity, but it might be worth keeping the bug open to state that there's something fishy. Lucas
Hi Lucas I'll keep the bug report open but will downgrade it to avoid removal from testing. Regards, Michael
We believe that the bug you reported is fixed in the latest version of
rsyslog, 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 1094069@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Michael Biebl <biebl@debian.org> (supplier of updated rsyslog 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: Wed, 19 Nov 2025 20:56:34 +0100
Source: rsyslog
Architecture: source
Version: 8.2510.0-4
Distribution: unstable
Urgency: medium
Maintainer: Michael Biebl <biebl@debian.org>
Changed-By: Michael Biebl <biebl@debian.org>
Closes: 1094069
Changes:
rsyslog (8.2510.0-4) unstable; urgency=medium
.
* Skip tests based on omfwd-lb-1target-retry-test_skeleton.sh and
omfwd-lb-1target-retry-test_skeleton-TargetFail.sh.
Those tests appear to be flaky and fail rather often on
reproducible-builds.org, especially on arm64.
See https://github.com/rsyslog/rsyslog/issues/6308 (Closes: #1094069)
Checksums-Sha1:
572db7a6b36f18aac0995561a4b2e1afb0eaa945 3626 rsyslog_8.2510.0-4.dsc
d45339b3f8b5db47b5e7b9001c34ce935295ea96 681820 rsyslog_8.2510.0-4.debian.tar.xz
b1e5e8b5cb995fffca63e0bf4b150b627d32f5c3 7425 rsyslog_8.2510.0-4_source.buildinfo
Checksums-Sha256:
2905c315e28b3d4b33d908bbad12270e8943e80f98302e817a6b404b9dd5aedc 3626 rsyslog_8.2510.0-4.dsc
1bbcd9faec74d5ab80b9b8ac99bd790ea87b54b1b9404822ece34a2112652404 681820 rsyslog_8.2510.0-4.debian.tar.xz
0a2f3a42bab23c8da7fc1b3d9920bde694e7a815a94fb7e07e9213d0e5b1cbb3 7425 rsyslog_8.2510.0-4_source.buildinfo
Files:
be93dde03f7c543586d8def87bf50a9b 3626 admin optional rsyslog_8.2510.0-4.dsc
60a8635bfb52d65964fc4c8f9eecf50d 681820 admin optional rsyslog_8.2510.0-4.debian.tar.xz
be7ee1becaa8a86135e6bddc41c7dc23 7425 admin optional rsyslog_8.2510.0-4_source.buildinfo
-----BEGIN PGP SIGNATURE-----
iQIzBAEBCgAdFiEECbOsLssWnJBDRcxUauHfDWCPItwFAmkeJ1UACgkQauHfDWCP
Itx8+Q/+Pe8cX5SkNigQEcEZRAOHngduhdjqEg0EYrZ7271yZ8PtDeG2IF4KT2y7
XkEWFmjjzS60AbBEnlImKQnpZYoIWF7GVRhVYuyRHVw+8/V1nc+HPGwiqtK5NIPD
wM/SHeqEPw84SXKQm2uHqqXr100vycgPuv6as5nwoz6XuprmNWN5D71H/VJtpX54
GPUKWlCFIQUqhSYltkPdv52vKPaehot3VFOFi/4GbDxYWq7oMRLPFS8+1+WktXuC
UPP5ZK3xavYzuE8+JOaPoIsgU1XKlYKskct2776+TY8BKHEr6c9InaG9x0JdSRwj
CZeBwav4VIL8k7QbW29w1vAZybewmPwOjJQSwtRsfnG3nIucgHizJJzwuqxnfg6r
BB9m2YPpCCrnIFwI4DJqwzc0tpc4z0K1Gdgdt/tPdDlqpZ6hb/VLQ0asDX4IJqFC
27FwTg5Q6JStST9HJ8Il8AwG/s5qOsqC21z0stjGdsQ+PMaXlXoj4KdHoF0IfqAc
mcY0cCXYhpvRPoETaJnyLCmlvxvuxkLAVPK/PagV/Q9qDV6AYojhTsgbBTGFUl5x
cJ1KDPl3lO54uIFPP+zQhc6OI8gmcOov5/TDxuyBpfm+lGwiwmNvxb2q3IDZDAmJ
OwJpd98KUrJhlVLD/i1bbzvoQadhmYPut4bG4/EEngs8F9hI9Mo=
=omiJ
-----END PGP SIGNATURE-----