Skip to content

Bumping POM dependencies, setting DNS server #1346

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

Merged
merged 1 commit into from
Feb 7, 2017

Conversation

Diagoras
Copy link
Contributor

@Diagoras Diagoras commented Feb 7, 2017

Adding some properties to the POM to set the DNS server used in tests to Google's. This will hopefully make builds more consistently reproducible, especially for people like me who have an ISP that likes to mess with the responses for incorrect DNS queries. :(

Also bumped the versions of the various Maven plugins, because why not?

@slandelle slandelle merged commit c1e66af into AsyncHttpClient:master Feb 7, 2017
@slandelle
Copy link
Contributor

@Diagoras thanks!

@slandelle slandelle added this to the 2.0.29 milestone Feb 7, 2017
@stepancheg
Copy link
Contributor

Because of this commit, tests fail on OSX on my notebook. Because "localhost" becomes "localhost.yandex.ru" (because "yandex.ru" is in the list of search domains in my network setup), which is resolved to 213.180.204.242 via 8.8.8.8.

I'd revert this commit.

@slandelle
Copy link
Contributor

slandelle commented Mar 28, 2017

@stepancheg As you might know, the DNS related modules are backports from Netty 4.1. So your problem actually happens upstream and you're probably not able to run Netty tests either.
I'd rather fix things upstream. Basically, I think those failing tests should ignore search domains.

ping @normanmaurer

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

Successfully merging this pull request may close these issues.

3 participants