-
Notifications
You must be signed in to change notification settings - Fork 4.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
dfp: adding a pause test #17580
dfp: adding a pause test #17580
Conversation
Signed-off-by: Alyssa Wilk <alyssar@chromium.org>
/wait |
/wait for tsan debug |
ASSERT_TRUE(fake_upstreams_[0]->waitForHttpConnection(*dispatcher_, fake_upstream_connection_)); | ||
ASSERT_TRUE(fake_upstream_connection_->waitForNewStream(*dispatcher_, upstream_request_)); | ||
ASSERT_FALSE(upstream_request_->waitForData(*dispatcher_, 1, std::chrono::milliseconds(100))); | ||
} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This test isn't representative, because DNS is immediately resolved, and dynamic-forward-proxy
resumes before processing body, so buffer-body-filter
never had a chance to pause it:
decode headers called: filter=0x15b9fdbcae00 status=0 // buffer headers (continue)
decode headers called: filter=0x15b9fdbf1f10 status=4 // dfp headers (pause)
continuing filter chain: filter=0x15b9fdbf1f10 // dfp headers (continue)
decode headers called: filter=0x15b9fe1019d0 status=1 // router headers
decode data called: filter=0x15b9fdbcae00 status=1 // buffer body (pause)
Compare with the reported issue (#17514 (comment)):
decode headers called: filter=0x444afcea08c0 status=0 // wasm headers (continue)
decode headers called: filter=0x444afcea09a0 status=4 // dfp headers (pause)
decode data called: filter=0x444afcea08c0 status=1 // wasm body (pause)
decode data called: filter=0x444afcea08c0 status=1 // wasm body (pause)
continuing filter chain: filter=0x444afcea09a0 // dfp headers (continue)
decode headers called: filter=0x444afcea0a10 status=1 // router headers
decode data called: filter=0x444afcea09a0 status=0 // dfp body (continue)
decode data called: filter=0x444afcea0a10 status=3 // router body
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It looks like we may need a custom filter to test this case.
/wait |
Risk Level: n/a (test only)
Testing: yes
Docs Changes: n/a
Release Notes: n/a
Part of #17514