integration runner: add --max-failures flag to cap test output #548
Open
integration runner: add --max-failures flag to cap test output #548
Conversation
…ilure Add a new -M / --max-failures flag (default: 100) that stops the test sequence once the failure count reaches the configured threshold. When triggered, workers are cancelled via context and a clear message is printed: ABORTED: too many failures (100), test sequence stopped early This prevents the result artifact from growing to hundreds of MB when Erigon is completely broken in a PR — only the first N diffs are written to disk. Set --max-failures 0 to restore unlimited behaviour. Also fix a stale test assertion for trace_rawTransaction which was removed from the default skip list in a previous PR but the test was not updated. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
canepat
approved these changes
Apr 13, 2026
canepat
changed the title
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.
Add a new -M / --max-failures flag (default: 100) that stops the test sequence once the failure count reaches the configured threshold. When triggered, workers are cancelled via context and a clear message is printed:
ABORTED: too many failures (100), test sequence stopped early
This prevents the result artifact from growing to hundreds of MB when Erigon is completely broken in a PR — only the first N diffs are written to disk. Set --max-failures 0 to restore unlimited behaviour.
Also fix a stale test assertion for trace_rawTransaction which was removed from the default skip list in a previous PR but the test was not updated.