Your message dated Fri, 3 Mar 2023 16:16:13 +0100
with message-id
<CA+6XHwRgGpgtqwBy2OPvcH9xFw=nuf_sgwxikyg2uqrmxyx...@mail.gmail.com>
and subject line Re: libstatgen: FTBFS on arm64: E: Build killed with signal
TERM after 150 minutes of inactivity
has caused the Debian Bug report #976570,
regarding libstatgen: FTBFS on arm64: E: Build killed with signal TERM after
150 minutes of inactivity
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 [email protected]
immediately.)
--
976570: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=976570
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Source: libstatgen
Version: 1.0.14-7
Severity: serious
Justification: FTBFS on arm64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20201205 ftbfs-bullseye
Hi,
During a rebuild of all packages in sid, your package failed to build
on arm64 (I don't know if it also fails on amd64).
Relevant part (hopefully):
> inputFileTest: InputFileTest.cpp:466: void
> IFILE_Test::test_ifread_ifgetc(const char*): Assertion `readChar == EOF'
> failed.
> Aborted
> make[4]: *** [../../../Makefiles/Makefile.test:53: test] Error 134
> make[3]: *** [Makefile:24: inputFileTest] Error 2
> make[3]: *** Waiting for unfinished jobs....
> g++ -O0 -pipe -Wall -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2
> -fdebug-prefix-map=/<<PKGBUILDDIR>>=. -fstack-protector-strong -Wformat
> -Werror=format-security -Wl,-z,relro -Wl,-z,now -I../../../include -I.
> -D__ZLIB_AVAILABLE__ -D_FILE_OFFSET_BITS=64 -D__STDC_LIMIT_MACROS -o
> cigarRollerTest obj/CigarRollerTest.o ../../../libStatGen_debug.a -lm -lz
> g++ -O0 -pipe -Wall -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2
> -fdebug-prefix-map=/<<PKGBUILDDIR>>=. -fstack-protector-strong -Wformat
> -Werror=format-security -Wl,-z,relro -Wl,-z,now -I../../../include -I.
> -D__ZLIB_AVAILABLE__ -D_FILE_OFFSET_BITS=64 -D__STDC_LIMIT_MACROS -o
> memoryMapArrayTest obj/MemoryMapArrayTest.o ../../../libStatGen_debug.a -lm
> -lz
> mkdir -p results; ./cigarRollerTest
>
> CigarRoller PASS: 646 FAIL: 0
> mkdir -p results; ./memoryMapArrayTest
> MemoryMapArrayTest PASS: 108 FAIL: 0
> g++ -O0 -pipe -Wall -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2
> -fdebug-prefix-map=/<<PKGBUILDDIR>>=. -fstack-protector-strong -Wformat
> -Werror=format-security -Wl,-z,relro -Wl,-z,now -I../../../include -I.
> -D__ZLIB_AVAILABLE__ -D_FILE_OFFSET_BITS=64 -D__STDC_LIMIT_MACROS -o
> referenceSequenceTest obj/ReferenceSequenceTest.o ../../../libStatGen_debug.a
> -lm -lz
> ./referenceSequenceTest
> test2 sequence utilization is 6.25% - expect around 6.25%
> E: Build killed with signal TERM after 150 minutes of inactivity
The full build log is available from:
http://qa-logs.debian.net/2020/12/05/libstatgen_1.0.14-7_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!
If you reassign this bug to another package, please marking 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 me
so that we can identify if something relevant changed in the meantime.
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.
--- End Message ---
--- Begin Message ---
Le mar. 15 déc. 2020 à 07:49, Dylan Aïssi <[email protected]> a écrit :
>
> arm64 is not on the architecture list for libstatgen, so I decrease
> the severity of the bug.
>
I close the bug for the same reason: arm64 is not in the architecture list.
Dylan
--- End Message ---
