Red Hat Bugzilla – Bug 1313393
Test suite failure: posix/tst-getaddrinfo5
Last modified: 2017-07-27 08:03:56 EDT
On 32-bit armv7hl the posix/tst-getaddrinfo5 test failus with:
resolving "localhost." failed, skipping this hostname
resolving "www.gnu.org." failed, skipping this hostname
This is odd, but perhaps the builders have a restricted build environment.
We should investigate this and consider rewriting the test.
Also seen on on x86_64.
Also seeon on i686.
This test should really fail everywhere. If it does not, it means the builder has working DNS resolution and potentially more extensive Internet access, which is not what we want.
We can fix this test easily once we have the resolver harness integrated.
(In reply to Florian Weimer from comment #3)
> This test should really fail everywhere. If it does not, it means the
> builder has working DNS resolution and potentially more extensive Internet
> access, which is not what we want.
> We can fix this test easily once we have the resolver harness integrated.
Agreed, we shouldn't be doing any testing that involves resolving names externally outside of the test framework.
This message is a reminder that Fedora 24 is nearing its end of life.
Approximately 2 (two) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 24. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora 'version'
Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version.
Thank you for reporting this issue and we are sorry that we were not
able to fix it before Fedora 24 is end of life. If you would still like
to see this bug fixed and are able to reproduce it against a later version
of Fedora, you are encouraged change the 'version' to a later Fedora
version prior this bug is closed as described in the policy above.
Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.
Upstream will fix this eventually as part of more extensive container-based testing.