ci: Run GUI unit tests in cross-Windows task #33919

1. 
   maflcko commented at 9:38 pm on November 20, 2025: member

   Most users of the cross-compiled releases for Windows will most likely pick the GUI, so running the cross-compiled GUI unit tests on a real Windows seems desirable.
2. ci: Run GUI unit tests in cross-Windows task fa7ea497c3
3. DrahtBot added the label Tests on Nov 20, 2025
4. 
   DrahtBot commented at 9:39 pm on November 20, 2025: contributor

   The following sections might be updated with supplementary metadata relevant to reviewers and maintainers.

   Code Coverage & Benchmarks

   For details see: https://corecheck.dev/bitcoin/bitcoin/pulls/33919.

   Reviews

   See the guideline for information on the review process.

   Type	Reviewers
   ACK	fanquake

   If your review is incorrectly listed, please react with 👎 to this comment and the bot will ignore it on the next update.

5. 
   maflcko commented at 10:25 pm on November 20, 2025: member

   Hmm, the CI did not fail, but I also do not see the expected output ********* Start testing of AppTests *********... etc, so I am not sure if everything worked here.
6. 
   Sammie05 commented at 0:59 am on November 21, 2025: none

   The workflow correctly attempts to execute the GUI test binary, ./bin/test_bitcoin-qt.exe. but the CI logs do not show any Qt test output and there are no lines such as ********* Start testing of ********* PASS / FAIL entries ********* Finished testing of *********

   It would be helpful to confirm that test_bitcoin-qt.exe is executing as intended

7. DrahtBot added the label CI failed on Nov 24, 2025
8. 
   DrahtBot commented at 11:11 am on November 24, 2025: contributor

   🚧 At least one of the CI tasks failed. Task macOS native: https://github.com/bitcoin/bitcoin/actions/runs/19630865894/job/56210087628 LLM reason (✨ experimental): test_bitcoin-qt test failed in the Qt test run, causing the CI to fail.

   Try to run the tests locally, according to the documentation. However, a CI failure may still happen due to a number of reasons, for example:

   • Possibly due to a silent merge conflict (the changes in this pull request being incompatible with the current code in the target branch). If so, make sure to rebase on the latest commit of the target branch.

   • A sanitizer issue, which can only be found by compiling with the sanitizer and running the affected test.

   • An intermittent issue.

   Leave a comment here, if you need help tracking down a confusing failure.

9. 
   maflcko commented at 11:14 am on November 24, 2025: member

   Looks like the output is missing, but this works: https://github.com/bitcoin/bitcoin/actions/runs/19630865894/job/56211087066#step:8:206:

   0Run ./bin/test_bitcoin-qt.exe
   1Error: Process completed with exit code 1.
   

10. maflcko force-pushed on Nov 24, 2025
11. DrahtBot removed the label CI failed on Nov 24, 2025
12. fanquake approved
13. 
    fanquake commented at 12:20 pm on November 25, 2025: member

    ACK fa7ea497c3ef9366805e520205f2acf04d4d347b - didn’t test.
14. fanquake merged this on Nov 25, 2025
15. fanquake closed this on Nov 25, 2025

    ---

16. maflcko deleted the branch on Nov 25, 2025
17. 
    hebasto commented at 5:26 pm on November 26, 2025: member

    Looks like the output is missing…

    The same happens for the native build: https://github.com/hebasto/bitcoin/actions/runs/19707163063/job/56457637457.

    It seems to be a peculiarity of the GHA Windows image.

Contributors
maflcko DrahtBot Sammie05 fanquake hebasto

Labels
Tests