Remove unreliable test cases about resolving supposedly invalid addresses #706
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
As I noted in #704 (comment), these tests are failing on my machine, as presumably my ISP provides a fallback IP when resolving nonexistent addresses.
Since we can't rely on the address resolution available in the environment used to run the tests, I don't think we can really test the "sad path" of attempting to resolve a supposedly invalid address. So, we should just remove these tests, at least for now, to unblock releasing JeroMQ 0.5.1. (see #704)