ci: port fuzzer-address-undefined-integer-nodepends
What the developer wrote
Authored by will
ci: port fuzzer-address-undefined-integer-nodepends
Co-authored-by: Max Edwards <youwontforgetthis@gmail.com>
What changed, and why it matters
This commit adds a new continuous-integration (CI) job to Bitcoin Core's GitHub Actions workflow. It runs the project's fuzz tests with AddressSanitizer, UndefinedBehaviorSanitizer, and IntegerSanitizer enabled, using the existing native fuzzing environment. There is no code change to Bitcoin Core itself, no bug fix, and no security patch.
No security action required. Treat as routine CI infrastructure maintenance.
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 ‘fuzzer,address,undefined,integer, no depends’. It reuses the existing 00_setup_env_native_fuzz.sh environment with a 240-minute timeout and specifies Cirrus/Ubuntu runners. This is purely an expansion of CI test coverage; it does not modify source code, dependencies, build logic, or runtime behavior.
Changed components
.github/workflows/ci.ymlInspect captured patch +6 / −0
diff --git a/.github/workflows/ci.yml b/.github/workflows/ci.yml
index 0cf29108..55520ffc 100644
--- a/.github/workflows/ci.yml
+++ b/.github/workflows/ci.yml
@@ -457,6 +457,12 @@ jobs:
timeout-minutes: 120
file-env: './ci/test/00_setup_env_i686_no_ipc.sh'
+ - name: 'fuzzer,address,undefined,integer, no depends'
+ cirrus-runner: 'ghcr.io/cirruslabs/ubuntu-runner-amd64:24.04-lg'
+ fallback-runner: 'ubuntu-24.04'
+ timeout-minutes: 240
+ file-env: './ci/test/00_setup_env_native_fuzz.sh'
+
steps:
- name: Checkout
uses: actions/checkout@v5
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.