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

Fix failing test in ServerAddressPropertyEditorUnitTests. [DATAMONGO-1062] #1983

Closed
spring-projects-issues opened this issue Sep 30, 2014 · 4 comments

Comments

@spring-projects-issues
Copy link

@spring-projects-issues spring-projects-issues commented Sep 30, 2014

Thomas Darimont opened DATAMONGO-1062 and commented

The test rejectsAddressConfigWithoutASingleParsableServerAddress fails because the supposedly non-existing hostname "bar" "now" resolves to a real host-address:

tom@gauss ~/Documents/dev/repos/spring/spring-data-mongodb (master●)$ ping bar
PING bar (127.0.53.53): 56 data bytes
Request timeout for icmp_seq 0

Affects: 1.6 GA (Evans)

Reference URL: http://stackoverflow.com/questions/25662590/domain-foo-bar-points-127-0-53-53-why

Referenced from: pull request #229

Backported to: 1.6.1 (Evans SR1), 1.5.5 (Dijkstra SR5)

@spring-projects-issues
Copy link
Author

@spring-projects-issues spring-projects-issues commented Sep 30, 2014

Thomas Darimont commented

Fixed test and added sanity check, please revise

@spring-projects-issues
Copy link
Author

@spring-projects-issues spring-projects-issues commented Sep 30, 2014

Thomas Darimont commented

This can be backported to 1.6 as well as 1.5

@spring-projects-issues
Copy link
Author

@spring-projects-issues spring-projects-issues commented Sep 30, 2014

Thomas Darimont commented

Backporting...

@spring-projects-issues
Copy link
Author

@spring-projects-issues spring-projects-issues commented Oct 1, 2014

Thomas Darimont commented

Back-ported to 1.6.x, 1.5.x

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

Successfully merging a pull request may close this issue.

None yet
2 participants