ci: failures in cross-built Windows CI #32197

1. 
   fanquake commented at 5:12 am on April 2, 2025: member

   Seen in https://github.com/bitcoin/bitcoin/actions/runs/14209827577/job/39815242086:

   0 ./test/util_tests.cpp(570): Entering test case "util_time_GetTime"
   1./test/util_tests.cpp(593): error: in "util_tests/util_time_GetTime": check steady_ms_0 < Now<SteadyMilliseconds>() has failed
   2./test/util_tests.cpp(594): error: in "util_tests/util_time_GetTime": check steady_0 + 1ms <= std::chrono::steady_clock::now() has failed
   3./test/util_tests.cpp(595): error: in "util_tests/util_time_GetTime": check ms_0 < GetTime<std::chrono::milliseconds>() has failed
   4./test/util_tests.cpp(570): Leaving test case "util_time_GetTime"; testing time: 34870us
   

2. fanquake added the label Windows on Apr 2, 2025
3. 
   maflcko commented at 8:27 am on April 2, 2025: member

   Reminds me of the other clock issue on Windows, which is still present today and only worked around by not using the clock at all in that wallet RPC: https://github.com/bitcoin/bitcoin/issues/25482
4. 
   maflcko commented at 8:32 am on April 2, 2025: member

   According to https://en.cppreference.com/w/cpp/thread/sleep_for, the implementation may take clock adjustments into account. So I guess the failure here is expected.

   So a possible fix would be to implement the sleep oneself.

5. 
   maflcko commented at 10:55 am on April 7, 2025: member

   After discussion in #32199 (comment), it is unclear why this fails and how to fix it.

   Also, as discussed, the test isn’t too important, so it could just be removed.

6. maflcko added the label Tests on Apr 7, 2025
7. maflcko added the label CI failed on Apr 7, 2025

Contributors
fanquake maflcko

Labels
Windows Tests CI failed