ci: Enable experimental kernel stuff in valgrind task
What changed, and why it matters
This commit changes only a continuous integration (CI) test script. It switches the valgrind test job to use a developer build preset and explicitly turns on experimental Bitcoin kernel-related components for testing. There is no change to the actual Bitcoin Core software that users run, and nothing in the commit suggests a security fix or vulnerability.
No security action needed. Treat as a normal CI/build-system change.
Security signals we found
No strong security signals were identified.
Evidence from the diff
The diff modifies ci/test/00_setup_env_native_valgrind.sh. It replaces explicit CMake options (-DWITH_ZMQ=ON -DBUILD_GUI=OFF) with –preset=dev-mode, keeps the GUI disabled, disables USDT explicitly, and by virtue of the dev-mode preset enables bitcoin-chainstate, libbitcoinkernel, and kernel-test experimental components for the valgrind CI task. This is a CI configuration change only.
Changed components
ci/test/00_setup_env_native_valgrind.shInspect captured patch +3 / −1
diff --git a/ci/test/00_setup_env_native_valgrind.sh b/ci/test/00_setup_env_native_valgrind.sh
index d6c45755..884bc395 100755
--- a/ci/test/00_setup_env_native_valgrind.sh
+++ b/ci/test/00_setup_env_native_valgrind.sh
@@ -17,5 +17,7 @@ export TEST_RUNNER_EXTRA="--exclude rpc_bind,feature_bind_extra"
export GOAL="install"
# TODO enable GUI
export BITCOIN_CONFIG="\
- -DWITH_ZMQ=ON -DBUILD_GUI=OFF \
+ --preset=dev-mode \
+ -DBUILD_GUI=OFF \
+ -DWITH_USDT=OFF \
"
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.