-
Notifications
You must be signed in to change notification settings - Fork 3.6k
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
test: fix flaky tests + new method RetryForBlocks #14609
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.
This is great! How do you decide how many blocks you need to wait in tests?
Now that you call tm it closes this right: #14520? |
It's an arbitrary number tbh, just a safe guess I suppose. I don't think a tx would take more than 2 blocks, but to be safe I've used 3. You will get the response before that if it's available anyway. There's one that has 10 blocks because there was a comment using that My strategy would be that any time we encounter a flaky test, we replace the |
@Mergifyio backport release/v0.47.x |
✅ Backports have been created
|
Co-authored-by: Marko <[email protected]> (cherry picked from commit 7505c18) # Conflicts: # CHANGELOG.md # testutil/network/network.go
…15469) Co-authored-by: Facundo Medica <[email protected]> Co-authored-by: marbar3778 <[email protected]>
Description
Closes: #14520
Author Checklist
All items are required. Please add a note to the item if the item is not applicable and
please add links to any relevant follow up issues.
I have...
!
to the type prefix if API or client breaking changeCHANGELOG.md
Reviewers Checklist
All items are required. Please add a note if the item is not applicable and please add
your handle next to the items reviewed if you only reviewed selected items.
I have...
!
in the type prefix if API or client breaking change