test: adding HTTP/3 fail socket write test#19171
Merged
yanavlasov merged 4 commits intoenvoyproxy:mainfrom Dec 2, 2021
Merged
Conversation
Signed-off-by: Alyssa Wilk <alyssar@chromium.org>
Contributor
Author
|
cc @danzh2010 that ended up being more involved than I thought, but I think we can use this for #19144 |
yanavlasov
reviewed
Dec 2, 2021
| testEnvoyProxying1xx(false, false, true); | ||
| } | ||
|
|
||
| TEST_P(ProtocolIntegrationTest, EnvoyProxying102) { |
Contributor
There was a problem hiding this comment.
Was this test pruning intentional?
Signed-off-by: Alyssa Wilk <alyssar@chromium.org>
Signed-off-by: Alyssa Wilk <alyssar@chromium.org>
Contributor
Author
|
/wait |
Signed-off-by: Alyssa Wilk <alyssar@chromium.org>
yanavlasov
approved these changes
Dec 2, 2021
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.
Extending the socket override framework to work for HTTP/3 and using it in the failed write test.
Risk Level: n/a (test only)
Testing: yep
Docs Changes: n/a
Release Notes: n/a