Package: src:libtest-redisserver-perl Version: 0.23-1 Severity: serious Tags: ftbfs trixie sid
Dear maintainer: During a rebuild of all packages in unstable, your package failed to build: -------------------------------------------------------------------------------- [...] debian/rules clean test -x debian/rules cd . && ./Build realclean /bin/sh: 1: ./Build: not found make: [/usr/share/cdbs/1/class/perl-build.mk:107: clean] Error 127 (ignored) rm -f debian/stamp-perl-build debian/stamp-perl-check dh_clean rm -f Makefile.old debian/rules binary test -x debian/rules dh_testroot dh_prep dh_installdirs -A mkdir -p "." cd . && perl -I. Build.PL --installdirs vendor --config ccflags="-g -O2 -Werror=implicit-function-declaration -ffile-prefix-map=/<<PKGBUILDDIR>>=. -fstack-protector-strong -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -D_REENTRANT -D_GNU_SOURCE -DDEBIAN -fwrapv -fno-strict-aliasing -pipe -I/usr/local/include -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64" --config cxxflags="-g -O2 -ffile-prefix-map=/<<PKGBUILDDIR>>=. -fstack-protector-strong -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection" --config cppflags="-Wdate-time -D_FORTIFY_SOURCE=2 -D_REENTRANT -D_GNU_SOURCE -DDEBIAN -fwrapv -fno-strict-aliasing -pipe -I/usr/local/include" --config lddlflags="-Wl,-z,relro -shared -L/usr/local/lib -fstack-protector-strong" --destdir /<<PKGBUILDDIR>>/debian/libtest-redisserver-perl Creating new 'Build' script for 'Test-RedisServer' version '0.23' cd . && ./Build build cp lib/Test/RedisServer.pm blib/lib/Test/RedisServer.pm touch debian/stamp-perl-build cd . && ./Build test --verbose 1 t/basic.t ......... ok 1 - pid ok ok 2 - unix socket ok ok 3 - server key does not exist ok ok 4 - ping pong ok ok 5 - pid removed ok ok 6 - no server available ok ok 7 - pid ok ok 8 - sock does not exist ok ok 9 - server addr ok ok 10 - ping pong ok ok 11 - server died ok 1..11 ok t/manual_start.t .. ok 1 - redis client object was not created ok ok 2 - error msg ok ok 3 - ping pong ok 1..3 ok t/no_save.t ....... ok 1 - pid ok ok 2 ok 3 - redis exit ok 1..3 ok t/no_server.t ..... ok 1 - server was not created ok ok 2 - error msg ok 1..2 ok t/tmp_dir.t ....... 21937:C 24 May 2025 09:50:37.007 # WARNING Memory overcommit must be enabled! Without it, a background save or replication may fail under low memory condition. Being disabled, it can also cause failures without low memory condition, see https://github.com/jemalloc/jemalloc/issues/1328. To fix this issue add 'vm.overcommit_memory = 1' to /etc/sysctl.conf and then reboot or run the command 'sysctl vm.overcommit_memory=1' for this to take effect. 21937:C 24 May 2025 09:50:37.007 * oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo 21937:C 24 May 2025 09:50:37.007 * Redis version=8.0.0, bits=64, commit=00000000, modified=0, pid=21937, just started 21937:C 24 May 2025 09:50:37.007 * Configuration loaded 21937:M 24 May 2025 09:50:37.008 * Increased maximum number of open files to 10032 (it was originally set to 1024). 21937:M 24 May 2025 09:50:37.008 * monotonic clock: POSIX clock_gettime 21937:M 24 May 2025 09:50:37.008 * Running mode=standalone, port=39829. 21937:M 24 May 2025 09:50:37.008 * Server initialized 21937:M 24 May 2025 09:50:37.009 * Ready to accept connections tcp 21937:signal-handler (1748080237) Received SIGTERM scheduling shutdown... 21937:M 24 May 2025 09:50:37.009 * User requested shutdown... 21937:M 24 May 2025 09:50:37.009 * Saving the final RDB snapshot before exiting. 21937:M 24 May 2025 09:50:37.020 * DB saved on disk 21937:M 24 May 2025 09:50:37.020 # Redis is now ready to exit, bye bye... ok 1 - no files remained after server shutdown 1..1 ok # Failed test 'error msg ok' # at t/unknown_conf.t line 18. # '*** failed to launch redis-server *** # 21950:C 24 May 2025 09:50:37.220 # WARNING Memory overcommit must be enabled! Without it, a background save or replication may fail under low memory condition. Being disabled, it can also cause failures without low memory condition, see https://github.com/jemalloc/jemalloc/issues/1328. To fix this issue add 'vm.overcommit_memory = 1' to /etc/sysctl.conf and then reboot or run the command 'sysctl vm.overcommit_memory=1' for this to take effect. # 21950:C 24 May 2025 09:50:37.220 * oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo # 21950:C 24 May 2025 09:50:37.220 * Redis version=8.0.0, bits=64, commit=00000000, modified=0, pid=21950, just started # 21950:C 24 May 2025 09:50:37.220 * Configuration loaded # 21950:M 24 May 2025 09:50:37.220 * Increased maximum number of open files to 10032 (it was originally set to 1024). # 21950:M 24 May 2025 09:50:37.220 * monotonic clock: POSIX clock_gettime # 21950:M 24 May 2025 09:50:37.221 * Running mode=standalone, port=0. # 21950:M 24 May 2025 09:50:37.221 # Unresolved Configuration(s) Detected: # 21950:M 24 May 2025 09:50:37.221 # >>> 'unknown_key unknown_val' # 21950:M 24 May 2025 09:50:37.221 # Module Configuration detected without loadmodule directive or no ApplyConfig call: aborting # at t/unknown_conf.t line 11. # ' # doesn't match '(?^:\*\*\* FATAL CONFIG FILE ERROR( \([^\)]+\))? \*\*\*)' # Looks like you failed 1 test of 2. t/unknown_conf.t .. ok 1 - server did not initialize ok not ok 2 - error msg ok 1..2 Dubious, test returned 1 (wstat 256, 0x100) Failed 1/2 subtests t/wait.t .......... ok 1 - process exited ok 2 - no pid ok ok 3 - redis exit ok 1..3 ok Test Summary Report ------------------- t/unknown_conf.t (Wstat: 256 (exited 1) Tests: 2 Failed: 1) Failed test: 2 Non-zero exit status: 1 Files=7, Tests=25, 5 wallclock secs ( 0.03 usr 0.00 sys + 0.64 cusr 0.22 csys = 0.89 CPU) Result: FAIL make: *** [/usr/share/cdbs/1/class/perl-build.mk:84: debian/stamp-perl-check] Error 1 dpkg-buildpackage: error: debian/rules binary subprocess returned exit status 2 -------------------------------------------------------------------------------- The above is just how the build ends and not necessarily the most relevant part. If required, the full build log is available here: https://people.debian.org/~sanvila/build-logs/202505/ About the archive rebuild: The build was made on virtual machines from AWS, using sbuild and a reduced chroot with only build-essential packages. If you could not reproduce the bug please contact me privately, as I am willing to provide ssh access to a virtual machine where the bug is fully reproducible. If this is really a bug in one of the build-depends, please use reassign and add an affects on src:libtest-redisserver-perl, so that this is still visible in the BTS web page for this package. Thanks.
