Use EmbeddedChannel for client timeout tests #524
Merged
Conversation
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
Motivation: The ClientTimeoutTests were often flakey as they relied on waiting for specified times instead of reacting to signals. Modifications: Provide an internal init for ClientConnection which uses an EmbeddedChannel. Rewrite the ClientTimeoutTests to make use of this change. Result: ClientTimeoutTests are more reliable.
MrMage
approved these changes
Jul 24, 2019
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Motivation:
The ClientTimeoutTests were often flakey as they relied on waiting
for specified times instead of reacting to signals.
Modifications:
Provide an internal init for ClientConnection which uses an
EmbeddedChannel. Rewrite the ClientTimeoutTests to make use of
this change.
Result:
ClientTimeoutTests are more reliable.