-
Notifications
You must be signed in to change notification settings - Fork 11.7k
[indexer-alt-framework] flakey test fix #24491
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
base: main
Are you sure you want to change the base?
Conversation
… unlucky enough to not be able to process the first 11 checkpoints before saturation, we'll stall forever
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
5839699 to
d0a0aec
Compare
…xed the flakiness.. why is that?
…ther decrease the duration of this test.
…work and speed up this test
amnn
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.
Accepting to unblock the flaky test fix, but looking at the rest of the test, I still see
// Lenient check that not all checkpoints < 250 were committedI thought in the review we discussed not doing this because it would because it could fail with low probability and that instead we should control execution such that you can know precisely how many checkpoints are skipped?
That was indeed done. I'll remove the comment. |
Description
the default ingestion concurrency of 200 means that if the indexer is unlucky enough to not be able to process the first 11 checkpoints before saturation, we'll stall forever
Test plan
How did you test the new or updated feature?
Release notes
Check each box that your changes affect. If none of the boxes relate to your changes, release notes aren't required.
For each box you select, include information after the relevant heading that describes the impact of your changes that a user might notice and any actions they must take to implement updates.