-
Notifications
You must be signed in to change notification settings - Fork 3.9k
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
kvstreamer: extend a test to assert that the streamer is used #82671
Conversation
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.
Reviewed all commit messages.
Reviewable status: complete! 1 of 0 LGTMs obtained (waiting on @michae2)
TFTR! bors r+ |
Looks like the test might be flaky. bors r- |
Canceled. |
5a6eca0
to
d868bf9
Compare
The adjusted test started being flaky in rare circumstances due to join reader not behaving under memory pressure for the lookup join with ordering test case. Opened up #82693 to fix that and will merge this PR once that PR goes in. |
This commit extends an existing test which examines the trace of different queries to assert that the streamer is used in all cases when we expect. It also simplifies some of the queries as well as adjusts the workmem limit which got out of sync with the index join memory limiting behavior which was changed recently. Release note: None
d868bf9
to
817fac5
Compare
Should be good now. bors r+ |
Build succeeded: |
This commit extends an existing test which examines the trace of
different queries to assert that the streamer is used in all cases when
we expect. It also simplifies some of the queries as well as adjusts the
workmem limit which got out of sync with the index join memory limiting
behavior which was changed recently.
Fixes: #82646.
Release note: None