Fix for testutils.GetAvailablePort on Windows #1009
Merged
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.
On Windows, there is a significant wait when connecting to a local port that is not active. That causes the
testutils.GetAvailablePort
function, which has an assumption that a call tonet.Dial
will be very quick, to take much longer than the expected 5s (around 1 min).See related discussion here: golang/go#23366
Re-implemented using a ticker with timeout channel so the function will terminate after 5s regardless of the number of attempts that were able to be made in that period.