-
Notifications
You must be signed in to change notification settings - Fork 11.4k
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
Better test coverage for consensus adapter max_in_flight behavior #21569
base: main
Are you sure you want to change the base?
Conversation
The latest updates on your projects. Learn more about Vercel for Git ↗︎
2 Skipped Deployments
|
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's hard to predict if this will have any false positives but we can go with trial and error approach
6bc2315
to
27467eb
Compare
@@ -691,6 +692,31 @@ impl ConsensusAdapter { | |||
.ok(); // result here indicates if epoch ended earlier, we don't care about it | |||
} | |||
|
|||
async fn acquire_submit_semaphore(&self) -> SemaphorePermit { | |||
loop { | |||
match tokio::time::timeout(Duration::from_secs(5), async { |
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 (5s) seems inconsistent with the error message later (30s). I think it is safer to use 30s which should still be low enough in tests.
Attempt to find bugs in which pending consensus transactions are never marked as processed.