test: check if 100s is enough to avoid flaky tests#1993
Merged
Conversation
DSharifi
changed the title
DSharifi
approved these changes
Feb 5, 2026
pbeza
approved these changes
Feb 6, 2026
github-merge-queue
bot
removed this pull request from the merge queue due to failed status checks
Contributor
Author
|
@DSharifi it already happened. Even with a timeout of 100s, it failed https://github.com/near/mpc/actions/runs/21748901746/job/62741598753 in one of the tests creating lots of accounts. Wdyt about pivoting to the retry mechanism as originally proposed? |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This is a follow up to #1945 which seems to have introduced its own flaky test issue