Make ConnectTimeout test accept NoRouteToHostException #1526
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.
The
ConnectTimeout
test expects an exception of typeSocketTimeoutException
when connecting to the unroutable address10.255.255.1
. But at least on my host (Fedora 30, OpenJDK 1.8.0_212) the connection attempt actually throwsjava.net.NoRouteToHostException
.That is an entirely reasonable exception to throw in this case, but not the intent of the test.
I think the test is intended to time out while connecting to the unreachable address. But it relies on highly platform-dependent behaviour. In particular if there's any sort of negative caching in place the test may fast-fail:
rendering the test useless for the intended purpose.
I propose to treat this as a skipped test, per the associated pull request.
(I've also included a trivial fix for a normally-unreachable NPE I hit during testing here).