Bug#973526: FTBFS due to SIGABRT while running HTTP server tests, bug #973526
Op 10-11-2020 om 16:21 schreef Andrey Rahmatullin: Running 7 test cases... started daemon at port 5923 terminate called after throwing an instance of 'boost::wrapexcept' what(): resolve: Host not found (authoritative) Looks like it tries to resolve something, and that usually implies Internet access, as otherwise you could just connect to localhost? Accessing the Internet is forbidden during building. The test case tried to resolve "127.0.0.1" as host. I've changed that to "localhost" since adding a flag for boost to only interpret the value as numeric is not easy to add to the code. I've seen hosts where localhost is mapped to some other IP address in the range 127.0.0.0/255 Could this be the case on the particular build machine where the test failed? Anyway, I assume that using localhost will be sufficient to fix this problem. We'll see that shorly. regards, -maarten
Bug#973526: FTBFS due to SIGABRT while running HTTP server tests, bug #973526
On Tue, 10 Nov 2020 20:21:10 +0500, Andrey Rahmatullin wrote: > > >> what(): resolve: Host not found (authoritative) > Looks like it tries to resolve something, and that usually implies > Internet access, as otherwise you could just connect to localhost? > Accessing the Internet is forbidden during building. Or if the build ends up one of the ipv6-only buildds where resolving "localhost" can also fail. (Last example I've encountered: #974033) Cheers, gregor -- .''`. https://info.comodo.priv.at -- Debian Developer https://www.debian.org : :' : OpenPGP fingerprint D1E1 316E 93A7 60A8 104D 85FA BB3A 6801 8649 AA06 `. `' Member VIBE!AT & SPI Inc. -- Supporter Free Software Foundation Europe `- NP: Bettina Wegner: Meinetwegen signature.asc Description: Digital Signature
Bug#973526: FTBFS due to SIGABRT while running HTTP server tests, bug #973526
On Tue, Nov 10, 2020 at 05:17:26PM +0200, Juhani Numminen wrote: > Hi, > > Maarten L. Hekkelman as the package maintainer asked for my help with bug > #973526 > but I have to forward his request to debian-mentors. > > The package libzeep failed to build on amd64, apparently because of a SIGABRT > during > its HTTP server test. > https://buildd.debian.org/status/fetch.php?pkg=libzeep=amd64=5.0.0-3=1604607341=0 > > >> [0;39;49m>> test/http-test.cpp > >> test/http-test.cpp: In member function ‘void > >> connection_read::test_method()’: > >> test/http-test.cpp:74:17: note: ‘#pragma message: write test for > >> avail/used’ > >>74 | #pragma message "write test for avail/used" > >> | ^~~ > > building http-test > >> cd test; ./http-test > >> Running 7 test cases... > >> started daemon at port 5923 > >> terminate called after throwing an instance of > >> 'boost::wrapexcept' > >> what(): resolve: Host not found (authoritative) Looks like it tries to resolve something, and that usually implies Internet access, as otherwise you could just connect to localhost? Accessing the Internet is forbidden during building. -- WBR, wRAR signature.asc Description: PGP signature
Bug#973526: FTBFS due to SIGABRT while running HTTP server tests, bug #973526
Hi, Maarten L. Hekkelman as the package maintainer asked for my help with bug #973526 but I have to forward his request to debian-mentors. The package libzeep failed to build on amd64, apparently because of a SIGABRT during its HTTP server test. https://buildd.debian.org/status/fetch.php?pkg=libzeep=amd64=5.0.0-3=1604607341=0 >> [0;39;49m>> test/http-test.cpp >> test/http-test.cpp: In member function ‘void connection_read::test_method()’: >> test/http-test.cpp:74:17: note: ‘#pragma message: write test for avail/used’ >>74 | #pragma message "write test for avail/used" >> | ^~~ > building http-test >> cd test; ./http-test >> Running 7 test cases... >> started daemon at port 5923 >> terminate called after throwing an instance of >> 'boost::wrapexcept' >> what(): resolve: Host not found (authoritative) >> unknown location(0): [4;31;49mfatal error: in "webapp_7": signal: SIGABRT >> (application abort requested)[0;39;49m >> test/http-test.cpp(122): [1;36;49mlast checkpoint: "webapp_7" test >> entry[0;39;49m >> started daemon at port 3364 >> terminate called recursively >> unknown location(0): [4;31;49mfatal error: in "server_with_security_1": >> signal: SIGABRT (application abort requested)[0;39;49m >> test/http-test.cpp(159): [1;36;49mlast checkpoint: "server_with_security_1" >> test entry[0;39;49m There is an example of a successful build for arm64 log here: https://buildd.debian.org/status/fetch.php?pkg=libzeep=arm64=5.0.0-3=1604618196=0 What might the issue be and how to fix this FTBFS? Regards, Juhani Numminen
