test: retry tests that flake on transient RPC connection drops#1249
Merged
MoonBoi9001 merged 1 commit intoJul 13, 2026
Conversation
4 suites call a live Arbitrum Sepolia RPC endpoint, and its transient connection drops (socket hang up, ECONNRESET) have been failing CI runs on unrelated PRs. Failed tests in those suites now retry up to 2 times, with each error still logged before retrying.
tmigone
approved these changes
Jul 13, 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.
This PR makes failed tests retry up to 2 times in the 4 indexer-common suites that talk to a live Arbitrum Sepolia RPC endpoint (tap, cost-models, indexing-rules, and poi-disputes), so a momentary connection drop no longer fails a CI run. Each failure is still logged before retrying, so the flakes stay visible in job logs rather than being silently absorbed, and a genuinely broken test still fails after 3 attempts.
The motivation is concrete: over the last 2 days, 4 CI node jobs across 3 runs on 2 unrelated PRs failed with transient transport errors from that endpoint (socket hang up in poi-disputes, ECONNRESET in indexing-rules), each time in a different test, and each time green on rerun. Retries happen through jest, which re-runs the per-test setup hooks, so each attempt starts from the same clean database state the first attempt had.