ci: only run coveralls on one of the unittest tasks
What the developer wrote
Authored by SomberNight
ci: only run coveralls on one of the unittest tasks
coveralls has been quite flaky recently -- let's try to lower the number of CI tasks where it spreads the flakiness.
What changed, and why it matters
This commit is a routine tweak to the project's automated testing setup. It changes one line in the CI configuration so that the coveralls code-coverage reporting tool only runs on the Python 3.10 test job instead of on every test job. There is no change to Electrum's wallet code, cryptography, networking, or anything users interact with.
No security action needed. This is a benign CI-only change.
Security signals we found
No strong security signals were identified.
Evidence from the diff
The diff modifies .cirrus.yml, adding an extra condition to the coveralls_script step so it executes only when ELECTRUM_PYTHON_VERSION equals ‘3.10’. This is purely a CI reliability change intended to reduce flakiness from the coveralls service. No application code, dependencies, secrets, or build artifacts are altered.
Changed components
.cirrus.ymlInspect captured patch +1 / −1
diff --git a/.cirrus.yml b/.cirrus.yml
index c1a3529..8fbb19a 100644
--- a/.cirrus.yml
+++ b/.cirrus.yml
@@ -55,7 +55,7 @@ task:
-m pytest tests -v
- coverage report
coveralls_script:
- - if [ ! -z "$COVERALLS_REPO_TOKEN" ] ; then coveralls ; fi
+ - if [ ! -z "$COVERALLS_REPO_TOKEN" ] && [ "$ELECTRUM_PYTHON_VERSION" = "3.10" ] ; then coveralls ; fi
env:
LD_LIBRARY_PATH: contrib/_saved_secp256k1_build/
ELECTRUM_REQUIREMENTS_CI: contrib/requirements/requirements-ci.txt
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.