test: try other ipv6 localhost alternatives#4325
Closed
Uh oh!
There was an error while loading. Please reload this page.
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.
ubuntu1404-64has been having issues withtest-net-connect-options-ipv6fairly frequently. I'm not exactly sure why the IPv6localhostresolving is flaky on that particular machine (it could be the way its network is configured?), but being an Ubuntu system it typically has other IPv6 localhost hostnames.This change tries those special IPv6 hostnames first before trying
localhost. If those special hostnames fail to resolve and iflocalhostshould error withENOTFOUND, it retries several times before giving up.I'm hoping this is enough to fix things. I did perform a stress test on that particular node and it was ok on every run after this change.