ci: Run GUI unit tests in cross-Windows task
What changed, and why it matters
This commit simply adds one line to Bitcoin Core's automated CI (continuous integration) workflow so that the GUI unit tests for the Windows build are executed alongside existing tests. It is a testing infrastructure change, not a code change to the Bitcoin software itself, and has no direct security relevance.
No security action needed. This is a routine CI coverage improvement.
Security signals we found
No strong security signals were identified.
Evidence from the diff
The change modifies .github/workflows/ci.yml in the cross-Windows CI job. It adds ./bin/test_bitcoin-qt.exe to the shell script that runs compiled unit tests. This ensures the Qt/GUI test binary is exercised in the Windows cross-compilation CI task. No source code, build system logic, or runtime behavior of Bitcoin Core is changed.
Changed components
.github/workflows/ci.ymlInspect captured patch +1 / −0
diff --git a/.github/workflows/ci.yml b/.github/workflows/ci.yml
index 880cc90c..de7ef484 100644
--- a/.github/workflows/ci.yml
+++ b/.github/workflows/ci.yml
@@ -433,6 +433,7 @@ jobs:
- name: Run unit tests
# Can't use ctest here like other jobs as we don't have a CMake build tree.
run: |
+ ./bin/test_bitcoin-qt.exe
./bin/test_bitcoin.exe -l test_suite # Intentionally run sequentially here, to catch test case failures caused by dirty global state from prior test cases.
./src/secp256k1/bin/exhaustive_tests.exe
./src/secp256k1/bin/noverify_tests.exe
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.