Listen explicitly on localhost on heartbeat TCP tests #15583
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.
Some tests were requiring localhost to resolve to 127.0.0.1, but this is
not always the case. In some machines localhost resolve to other local
addresses as 127.0.1.1, or to [::1] if ipv4 is not available.
httptest.NewServer
always binds to127.0.0.1
, so connections tolocalhost can fail if localhost resolves to a different IP.
Explicitly use
localhost
when binding and later expecting name resolution.Issue seen in Travis when upgrading the Ubuntu image during the
migration to Python 3, can be reproduced by modifying
/etc/hosts
touse an IP different to
127.0.0.1
aslocalhost
.