Source: vmem Version: 1.8-1 Severity: serious Justification: FTBFS on amd64 Tags: bullseye sid ftbfs Usertags: ftbfs-20200802 ftbfs-bullseye
Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[4]: Entering directory '/<<PKGBUILDDIR>>/src/test' > out_err/TEST0: SETUP (check/debug) > out_err/TEST0: PASS [00.025 s] > out_err_mt/TEST0: SETUP (check/debug) > out_err_mt/TEST0: PASS [00.027 s] > out_err_mt/TEST0: SETUP (check/nondebug) > out_err_mt/TEST0: PASS [00.026 s] > out_err_mt/TEST1: SETUP (check/debug/drd) > out_err_mt/TEST1: PASS [00.589 s] > out_err_mt/TEST1: SETUP (check/nondebug/drd) > out_err_mt/TEST1: PASS [00.564 s] > out_err_mt/TEST2: SETUP (check/debug/helgrind) > out_err_mt/TEST2: PASS [00.534 s] > out_err_mt/TEST2: SETUP (check/nondebug/helgrind) > out_err_mt/TEST2: PASS [00.511 s] > scope/TEST0: SETUP (check/debug) > [MATCHING FAILED, COMPLETE FILE (out0.log) BELOW] > ../../debug/libvmem.so.1: > vmem_aligned_alloc@@LIBVMEM_1.0 > vmem_calloc@@LIBVMEM_1.0 > vmem_check@@LIBVMEM_1.0 > vmem_check_version@@LIBVMEM_1.0 > vmem_create@@LIBVMEM_1.0 > vmem_create_in_region@@LIBVMEM_1.0 > vmem_delete@@LIBVMEM_1.0 > vmem_errormsg@@LIBVMEM_1.0 > vmem_free@@LIBVMEM_1.0 > vmem_malloc@@LIBVMEM_1.0 > vmem_malloc_usable_size@@LIBVMEM_1.0 > vmem_realloc@@LIBVMEM_1.0 > vmem_set_funcs@@LIBVMEM_1.0 > vmem_stats_print@@LIBVMEM_1.0 > vmem_strdup@@LIBVMEM_1.0 > vmem_wcsdup@@LIBVMEM_1.0 > > [EOF] > out0.log.match:1 $(*) > out0.log:1 ../../debug/libvmem.so.1: > out0.log.match:2 vmem_aligned_alloc > out0.log:2 vmem_aligned_alloc@@LIBVMEM_1.0 > FAIL: match: out0.log.match:2 did not match pattern > RUNTESTS: stopping: scope/TEST0 failed, BUILD=debug > make[4]: *** [Makefile:158: check] Error 1 The full build log is available from: http://qa-logs.debian.net/2020/08/02/vmem_1.8-1_unstable.log 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! About the archive rebuild: The rebuild was done on EC2 VM instances from Amazon Web Services, using a clean, minimal and up-to-date chroot. Every failed build was retried once to eliminate random failures.
