ci: Enable `wallet_multiwallet.py` in "Windows, test cross-built" job
What changed, and why it matters
This commit simply re-enables an automated test (wallet_multiwallet.py) in the Windows cross-build continuous integration job. It removes the temporary exclusion that was put in place while a bug was being fixed. There is no change to Bitcoin Core's actual wallet code, network code, or consensus logic, so it does not affect users' funds, node security, or network behavior.
No security action required. Treat as a normal CI/test maintenance change.
Security signals we found
No strong security signals were identified.
Evidence from the diff
The diff removes two lines from .github/ci-windows-cross.py: a comment referencing GitHub issue #31409 and the corresponding –exclude wallet_multiwallet.py argument in the functional test runner invocation. This is a CI-only change that restores a previously disabled test after the underlying issue was resolved elsewhere. No source code, build system, or runtime behavior of Bitcoin Core is modified.
Changed components
.github/ci-windows-cross.pyCI test configuration for Windows cross-build jobInspect captured patch +0 / −3
diff --git a/.github/ci-windows-cross.py b/.github/ci-windows-cross.py
index 13ca3b49..fdda0394 100755
--- a/.github/ci-windows-cross.py
+++ b/.github/ci-windows-cross.py
@@ -97,9 +97,6 @@ def run_functional_tests():
# feature_unsupported_utxo_db.py fails on Windows because of emojis in the test data directory.
"--exclude",
"feature_unsupported_utxo_db.py",
- # See https://github.com/bitcoin/bitcoin/issues/31409.
- "--exclude",
- "wallet_multiwallet.py",
]
run(test_runner_cmd)
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.