ci: cd into BASE_BUILD_DIR for GetCMakeLogFiles
What changed, and why it matters
This is a minor fix to Bitcoin Core's internal continuous integration (CI) test script. When a CMake build fails, the script prints diagnostic log files. The change ensures the script changes into the build directory first so the helper that lists log files can find them correctly. It does not change the Bitcoin software users run, does not touch networking or cryptography, and has no security relevance for end users.
No security action needed. Treat as a normal CI/maintenance fix.
Security signals we found
No strong security signals were identified.
Evidence from the diff
In ci/test/03_test_script.sh, after a failed cmake configuration step, the script now runs cd "${BASE_BUILD_DIR}" before invoking cmake -P .../GetCMakeLogFiles.cmake to list and cat CMake error logs. This is a CI-only path correction to make log collection work; it affects neither the produced binaries nor any runtime behavior of Bitcoin Core.
Changed components
ci/test/03_test_script.shInspect captured patch +1 / −0
diff --git a/ci/test/03_test_script.sh b/ci/test/03_test_script.sh
index a5248b8d..18c7ab6a 100755
--- a/ci/test/03_test_script.sh
+++ b/ci/test/03_test_script.sh
@@ -131,6 +131,7 @@ if [[ "${RUN_TIDY}" == "true" ]]; then
fi
bash -c "cmake -S $BASE_ROOT_DIR -B ${BASE_BUILD_DIR} $BITCOIN_CONFIG_ALL $BITCOIN_CONFIG" || (
+ cd "${BASE_BUILD_DIR}"
# shellcheck disable=SC2046
cat $(cmake -P "${BASE_ROOT_DIR}/ci/test/GetCMakeLogFiles.cmake")
false
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.