test: Expand loopback range to address port exhaustion #5892
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.
High Level Overview of Change
This PR uses the entire loopback range 127.0.0.1 - 127.255.255.254 in unit tests for Linux and Windows. It also adds a necessary space after relevant error messages, and removes two gRPC config functions that are no longer in use.
Context of Change
When multiple unit tests are executed in parallel and in rapid succession, which is typical during busy periods of development in the CI pipelines, it is possible that there are no available ports on the default loopback address 127.0.0.1. As the entire 127.0.0.0/8 range (except 127.0.0.0 and 127.255.255.255) are available on Linux and Windows (but not on macOS), we can avoid the port exhaustion problem by picking any IP address from that range at random.
Type of Change
.gitignore
, formatting, dropping support for older tooling)