ci: Enable CI_LIMIT_STACK_SIZE=1 in i686_no_ipc task
What changed, and why it matters
This commit only changes a continuous integration (CI) test configuration file. It adds an environment variable that limits stack size during automated testing of a 32-bit Intel build. 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 required. This is a routine CI configuration change.
Security signals we found
No strong security signals were identified.
Evidence from the diff
The diff adds export CI_LIMIT_STACK_SIZE=1 to ci/test/00_setup_env_i686_no_ipc.sh, a CI environment setup script for an i686 (32-bit x86) no-IPC test task. This is a testing-harness configuration change. It does not modify source code, consensus logic, networking, wallet, or any runtime behavior of Bitcoin Core outside of CI.
Changed components
ci/test/00_setup_env_i686_no_ipc.shInspect captured patch +1 / −0
diff --git a/ci/test/00_setup_env_i686_no_ipc.sh b/ci/test/00_setup_env_i686_no_ipc.sh
index 5ab41437..4da38d9b 100755
--- a/ci/test/00_setup_env_i686_no_ipc.sh
+++ b/ci/test/00_setup_env_i686_no_ipc.sh
@@ -13,6 +13,7 @@ export CI_IMAGE_PLATFORM="linux/amd64"
export PACKAGES="llvm clang g++-multilib"
export DEP_OPTS="DEBUG=1 NO_IPC=1"
export GOAL="install"
+export CI_LIMIT_STACK_SIZE=1
export TEST_RUNNER_EXTRA="--v2transport --usecli"
export BITCOIN_CONFIG="\
-DCMAKE_BUILD_TYPE=Debug \
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.