Override retry times to fix unnecessarily long test runs#414
Merged
Conversation
maltejur
force-pushed
the
times_override
branch
3 times, most recently
from
9271001 to
c107ff0
Compare
Currently, running all tests takes a really long time because the `@retry` mechanism acts in places where we expect a failure. It seems like there already is a RETRY_TIMES override put in place to address this, but it wasn't actually utilized.
tomrittervg
approved these changes
Apr 8, 2026
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
2 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.
Currently, running all tests takes a really long time because the
@retrymechanism acts in places where we expect a failure. It seems like there already is a RETRY_TIMES override put in place to address this, but it wasn't actually utilized.Also do a general dependency update, as I am otherwise seeing linting failures.