CI: Disable flakiness tracking.
What changed, and why it matters
This commit simply turns off a test-reporting feature in the project's automated build system because it was making tests run very slowly and the reporting server appeared to be down. It does not change any wallet, network, or Lightning protocol code, and there is no security issue in the change itself.
No security action needed. If re-enabling the flakiness tracker in the future, review the plugin and server endpoint for data handling and availability, but that is outside the scope of this commit.
Security signals we found
No strong security signals were identified.
Evidence from the diff
The patch comments out the CI_SERVER_URL environment variable used by a pytest plugin that reported flaky test results to an external server. The commit message states the plugin slowed integration tests dramatically and the server was unreachable. No runtime, cryptographic, or protocol code is modified.
Changed components
.github/workflows/ci.yamlInspect captured patch +2 / −1
diff --git a/.github/workflows/ci.yaml b/.github/workflows/ci.yaml
index 9f384eaf..9e610d91 100644
--- a/.github/workflows/ci.yaml
+++ b/.github/workflows/ci.yaml
@@ -14,7 +14,8 @@ env:
# Reduce size, helps upload-artifact work more reliably
RUST_PROFILE: small
SLOW_MACHINE: 1
- CI_SERVER_URL: "http://35.239.136.52:3170"
+ # This is for the pytest-trackflaky:
+ # CI_SERVER_URL: "http://35.239.136.52:3170"
PYTEST_OPTS_BASE: "-vvv --junit-xml=report.xml --timeout=1800 --durations=10"
TEST_LOG_IGNORE_ERRORS: "1"
SCCACHE_GHA_ENABLED: "true"
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.