Tests that run dbus-daemon time out when run on Windows on Gitlab-CI
Several tests run a dbus-daemon
as a subprocess:
test/dbus-daemon.c
test/dbus-daemon-eavesdrop.c
test/header-fields.c
test/monitor.c
- (plus some more that are not applicable on Windows, therefore either skip all test-cases or are not compiled at all)
When the dbus test suite is run by the windows vs15-64 cmake
CI job (building and running x64 binaries on real Windows using CMake and Visual Studio 15), dbus-daemon*
and monitor
are skipped, with comment "a few tests timeout on gitlab runner for unknown reason" (added in !218 (merged) by @elmarco).
test/header-fields.c
is not built by CMake at all, only by Autotools (and now Meson). That's out of scope here: it would be an easy fix if someone wants to enable that, but perhaps not worth it if we're intending to remove CMake in favour of Meson.
The windows msys64 ucrt64 cmake
CI job (building and running x64 binaries on real Windows using MSYS for the build and UCRT for the binaries under test) doesn't run any tests, so we don't know whether it would succeed or not. Again, that's out of scope here, and possibly not worth it if CMake is on its way out. I suspect the answer is that these four tests would time out.
When we tried building and running the dbus test suite with Meson on !303 (merged) (this time building and running x86 binaries on real Windows using MSYS for the build and UCRT for the binaries under test, and building and running x64 binaries on real Windows using Visual Studio 15), these four tests also time out in those configurations.
Someone who likes Windows should investigate whether these tests run successfully on a developer's Windows machine (other than on Gitlab-CI) and whether they can be made to run successfully on Gitlab-CI. For now, I'm going to skip them in Meson builds, for parity with CMake.