Source: holes Version: 0.1-5 Severity: serious Justification: FTBFS Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-20240420 ftbfs-trixie ftbfs-t64-armhf
Hi, During a rebuild of all packages in sid, your package failed to build on armhf. Relevant part (hopefully): > make[1]: Entering directory '/<<PKGBUILDDIR>>' > prove -v ./tests > ./tests .. > 1..10 > ok - no hole > ok - big, no hole > ok - empty file > not ok - small holes > # Unexpected output: > # 00000011 0 > # 00000077 0 > ok - small, undetected holes > not ok - medium holes > # Unexpected output: > # 00000000 0 > # 00010000 0 > not ok - medium, offsetted holes > # Unexpected output: > # 00000000 0 > # 0000fffa 0 > not ok - huge holes > # Unexpected output: > # 00000000 0 > # 00c00000 0 > not ok - huge, offsetted holes > # Unexpected output: > # 00000e34 0 > # 00c00e34 0 > not ok - detect non-zeroes > # Unexpected output: > # 00000e34 0 > # 00c00e34 0 > Failed 6/10 subtests > > Test Summary Report > ------------------- > ./tests (Wstat: 0 Tests: 10 Failed: 6) > Failed tests: 4, 6-10 > Files=1, Tests=10, 1 wallclock secs ( 0.02 usr 0.00 sys + 0.20 cusr 0.54 > csys = 0.76 CPU) > Result: FAIL > make[1]: *** [Makefile:19: check] Error 1 > make[1]: Leaving directory '/<<PKGBUILDDIR>>' > dh_auto_test: error: make -j4 check returned exit code 2 The full build log is available from: http://qa-logs.debian.net/2024/04/20/holes_0.1-5_unstable-armhf.log All bugs filed during this archive rebuild are listed at: https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20240420;users=lu...@debian.org or: https://udd.debian.org/bugs/?release=na&merged=ign&fnewerval=7&flastmodval=7&fusertag=only&fusertagtag=ftbfs-20240420&fusertaguser=lu...@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.
