Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Dotted FQDN tests may fail or succeed depending on system DNS configuration #1809

Closed
mgorny opened this issue Mar 9, 2020 · 1 comment · Fixed by #1820
Closed

Dotted FQDN tests may fail or succeed depending on system DNS configuration #1809

mgorny opened this issue Mar 9, 2020 · 1 comment · Fixed by #1820

Comments

@mgorny
Copy link
Contributor

mgorny commented Mar 9, 2020

Related to #1475, #1648.

I've recently spent some time debugging test failures reported by Gentoo users, and came to the conclusion that resolving localhost. may work or not depending on the system resolver configuration. I've been able to make it work reliably by listing localhost. in /etc/hosts explicitly or by using nss_myhostname. It also may work when external DNS is used and works, though I have no clue why glibc makes it work like that. On the other hand, if the system can't connect to the DNS resolver, it fails.

Since this test is unreliable, could you please disable (skip) it by default and enable only on known-good travis infra? I would supply a patch but I don't really know what values TRAVIS_INFRA can have.

@sethmlarson
Copy link
Member

Yep I definitely run into this issue as well. Maybe we need to skip the test if we can't resolve localhost., change the decorator to run that DNS lookup and on failure just skip.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants