ci: fail fast in test-each-commit script
What the developer wrote
Authored by Lőrinc
ci: fail fast in test-each-commit script
Pass `--failfast` to the functional test runner in `.github/ci-test-each-commit-exec.py`.
Stop after the first failure to surface the root cause sooner and keep logs readable when testing ancestor commits.
Co-authored-by: MarcoFalke <*~=`'#}+{/-|&$^_@721217.xyz>
What changed, and why it matters
This change only adds a '--failfast' flag to Bitcoin Core's internal continuous integration script. It tells the test runner to stop after the first test failure instead of continuing. There is no security relevance: it does not change production code, network behavior, wallet handling, or any user-facing functionality.
No security action needed. Treat as a normal CI/development workflow improvement.
Security signals we found
No strong security signals were identified.
Evidence from the diff
The commit modifies .github/ci-test-each-commit-exec.py, a GitHub Actions helper, by appending ‘–failfast’ to the functional test runner invocation. This is a pure CI quality-of-life improvement to reduce log noise and surface root causes faster when testing each commit in a branch. It does not alter consensus, P2P, RPC, wallet, or cryptographic code.
Changed components
.github/ci-test-each-commit-exec.pyInspect captured patch +1 / −0
diff --git a/.github/ci-test-each-commit-exec.py b/.github/ci-test-each-commit-exec.py
index fcd3bbdb..66334b83 100755
--- a/.github/ci-test-each-commit-exec.py
+++ b/.github/ci-test-each-commit-exec.py
@@ -62,6 +62,7 @@ def main():
f"./{build_dir}/test/functional/test_runner.py",
"-j",
str(num_procs * 2),
+ "--failfast",
"--combinedlogslen=99999999",
])
Why this scored 15/100
Community notes
Notes can correct, qualify, or add evidence to the AI analysis. Every note shown here has been validated by a human moderator.
The AI analysis stands alone for now. Submit a note if you can add evidence or important context.