On 01/08/2023 15.49, Daniel P. Berrangé wrote: ...
If the value of the msys2 jobs is that they let us run the test suite, can we limit the usage of msys2 to just that part, and chain it upto the fedora mingw cross compile jobs ie.win64-fedora-cross-container | +-> cross-win64-system | +-> check-win64-msys In the "cross-win64-system" job we would have to publish the entire QEMU 'build' directory as an artifact, to pass it over to the msys job. If we also published /usr/x86_64-w64-mingw32/ as an artifact, then we would not need to install any mingw packages under msys. The basic msys installer can be run (which takes a couple of minutes), and then then we just dump the Fedora artifacts of /usr/x86_64-w64-mingw32/ into the right place and run the test suite.
It's a nice idea at a first glance - but at a second glance I doubt that this is easy to realize. You need the configured meson environment for running the tests, and you cannot easily pass that from the Fedora container to MSYS2. So you'd either need to re-run meson setup in the MSYS2 job and then trick it into believing that the binaries have already been built, or you have to run the test binaries "manually" without meson... both might be possible, but it sounds rather fragile to me.
Thomas
