-
-
Notifications
You must be signed in to change notification settings - Fork 15.8k
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
Netty DNS Tests fail with custom search domain #6966
Comments
Are you also setting the value of |
options ndots:2 is what I have |
yip makes sense ... I corrected the conditional above. Let me be more explicit about setting this in our unit tests. |
Motivation: The DNS resolver may use default configuration inherited from the environment. This means the ndots value may change and result in test failure if the tests don't explicitly set the assumed value. Modifications: - Explicitly set ndots in resolver-dns unit tests so we don't fail if the environment overrides the search domain and ndots Result: Unit tests are less dependent upon the enviroment they run in. Fixes netty#6966.
Please verify PR #6967 |
Motivation: The DNS resolver may use default configuration inherited from the environment. This means the ndots value may change and result in test failure if the tests don't explicitly set the assumed value. Modifications: - Explicitly set ndots in resolver-dns unit tests so we don't fail if the environment overrides the search domain and ndots Result: Unit tests are less dependent upon the enviroment they run in. Fixes netty#6966.
Motivation: The DNS resolver may use default configuration inherited from the environment. This means the ndots value may change and result in test failure if the tests don't explicitly set the assumed value. Modifications: - Explicitly set ndots in resolver-dns unit tests so we don't fail if the environment overrides the search domain and ndots Result: Unit tests are less dependent upon the enviroment they run in. Fixes netty#6966.
Expected behavior
tests pass
Actual behavior
tests fail
Steps to reproduce
Add this to
/etc/resolv.conf
:and run tests
Netty version
4.1
output:
Notice the floop domain added in the log messages.
The text was updated successfully, but these errors were encountered: