Repository navigation
Fix: stop the ping rewrite test from querying real DNS - #494
Merged
Merged
Conversation
The test faked dns.lookup only. Host names now resolve through dns.promises.Resolver and dns.promises.lookup, so the test queried the real DNS server and failed when it answered slowly.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Summary
dns.lookupfake inproxy-ping-rewrite.test.jswith fakes ofdns.promises.Resolver.prototype.resolve4/resolve6anddns.promises.lookup, the callsapi/src/resolve.jsmakes.Testing
All green. With a DNS server that never answers, the file takes 45 ms instead of stalling for 4 s.
Changelog
Checklist