-
Notifications
You must be signed in to change notification settings - Fork 9.1k
HDFS-16755. TestQJMWithFaults.testUnresolvableHostName() can fail due to unexpected host resolution #4833
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
Conversation
🎊 +1 overall
This message was automatically generated. |
LGTM. |
Could someone transform HADOOP-18431 to HDFS-*? |
… to unexpected host resolution Use ".invalid" domain from IETF RFC 2606 to ensure that the host doesn't resolve.
250d1a0
to
2afc87c
Compare
🎊 +1 overall
This message was automatically generated. |
@steveloughran I think I've addressed all of your earlier concerns. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
+1
… to unexpected host resolution (#4833) Use ".invalid" domain from IETF RFC 2606 to ensure that the host doesn't resolve. Contributed by Steve Vaughan Jr
… to unexpected host resolution (apache#4833) Use ".invalid" domain from IETF RFC 2606 to ensure that the host doesn't resolve.
… to unexpected host resolution (apache#4833) Use ".invalid" domain from IETF RFC 2606 to ensure that the host doesn't resolve. Contributed by Steve Vaughan Jr
Description of PR
Tests that want to use an unresolvable address may actually resolve in some environments. Replacing host names like "bogus" with a IETF RFC 2606 domain name avoids the issue.
Use ".invalid" domain from IETF RFC 2606 to ensure that the host "bogus" doesn't resolve.
How was this patch tested?
Test were executed through both Maven Surefire and the IDE to demonstrate that this change resulted in the expected test result.
For code changes:
LICENSE
,LICENSE-binary
,NOTICE-binary
files?