What changed, and why it matters
This commit simply adds a new automated testing job to Bitcoin Core's continuous integration (CI) pipeline. It will run the project's fuzz tests under Valgrind, a memory-error detection tool. There is no code change to Bitcoin Core itself, no bug fix, and no security vulnerability being patched.
No security action required. This is a routine CI/testing infrastructure change. Reviewers may optionally verify that the referenced environment script exists and that the runner resources and timeout are adequate.
Security signals we found
No strong security signals were identified.
Evidence from the diff
The diff adds one matrix entry to .github/workflows/ci.yml named ‘Valgrind, fuzz’. It references the existing CI environment script 00_setup_env_native_fuzz_with_valgrind.sh and runs on an Ubuntu 24.04 runner with a 240-minute timeout. This is purely an expansion of CI coverage for dynamic analysis of fuzz targets; it does not modify source code, consensus logic, networking, or wallet behavior.
Changed components
.github/workflows/ci.ymlInspect captured patch +6 / −0
diff --git a/.github/workflows/ci.yml b/.github/workflows/ci.yml
index 5d02d26a..a05e8f96 100644
--- a/.github/workflows/ci.yml
+++ b/.github/workflows/ci.yml
@@ -500,6 +500,12 @@ 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, depends DEBUG'
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.