Re: FTBFS due to SIGABRT while running HTTP server tests, bug #973526
Op 10-11-2020 om 16:21 schreef Andrey Rahmatullin:
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?
Running 7 test cases...
started daemon at port 5923
terminate called after throwing an instance of 'boost::wrapexcept<boost::system::system_error>'
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.
Anyway, I assume that using localhost will be sufficient to fix this
problem. We'll see that shorly.