- Notifications
You must be signed in to change notification settings - Fork213
test: fix streaming pull close test flakiness#361
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 ourterms of service andprivacy statement. We’ll occasionally send you account related emails.
Already on GitHub?Sign in to your account
Uh oh!
There was an error while loading.Please reload this page.
Conversation
Uh oh!
There was an error while loading.Please reload this page.
jimfulton left a comment
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.
I'm not sure what flakiness this is fixing.
On my machine, the system testtest_publish_large_messages still fails with a timeout on this branch. Maybe that's not what this PR is intended to address.
Uh oh!
There was an error while loading.Please reload this page.
plamut commentedApr 7, 2021 • edited
Loading Uh oh!
There was an error while loading.Please reload this page.
edited
Uh oh!
There was an error while loading.Please reload this page.
@jimfulton It fixes the flakiness inunit tests. If a system test covering the same code is now flaky, too, we should investigate that as well, but it's a separate issue (that test depends on some assumption about how the backend works). Edit: Created anissue to track that. |
jimfulton commentedApr 7, 2021
Oops, OK. :) |
Uh oh!
There was an error while loading.Please reload this page.
Fixes#352.
Fixes#373.
This PR fixes unit test flakiness by waiting for the streaming pull manager shutdown thread to finish running before making any assertions.
PR checklist