ci: Drop valgrind fuzz from GHA matrix
What changed, and why it matters
This commit simply removes one automated testing job from Bitcoin Core's GitHub Actions continuous integration setup. It does not change any Bitcoin node, wallet, or network code. There is no security vulnerability introduced or fixed here.
No security action needed. Project maintainers may want to document the rationale for dropping the Valgrind fuzz job and ensure equivalent coverage is provided elsewhere if desired.
Security signals we found
No strong security signals were identified.
Evidence from the diff
The diff deletes a single CI matrix entry named ‘Valgrind, fuzz’ from .github/workflows/ci.yml. That job ran the fuzzing test suite under Valgrind on every CI trigger. Removing it reduces CI coverage but does not modify source code, build scripts, test logic, or runtime behavior of the Bitcoin Core software.
Changed components
.github/workflows/ci.ymlInspect captured patch +0 / −6
diff --git a/.github/workflows/ci.yml b/.github/workflows/ci.yml
index ed0a77c2..1db4b4d5 100644
--- a/.github/workflows/ci.yml
+++ b/.github/workflows/ci.yml
@@ -578,12 +578,6 @@ jobs:
timeout-minutes: 240
file-env: './ci/test/00_setup_env_native_fuzz.sh'
- - name: 'Valgrind, fuzz'
- cirrus-runner: 'ghcr.io/cirruslabs/ubuntu-runner-amd64:24.04-md'
- fallback-runner: 'ubuntu-24.04'
- timeout-minutes: 240
- file-env: './ci/test/00_setup_env_native_fuzz_with_valgrind.sh'
-
- name: 'previous releases'
cirrus-runner: 'ghcr.io/cirruslabs/ubuntu-runner-amd64:24.04-md'
fallback-runner: 'ubuntu-24.04'
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.