Skip to content

Conversation

guusdk
Copy link
Member

@guusdk guusdk commented Aug 21, 2025

As we're producing binaries for Windows, and that OS notably differs from Linux in things like the representation of a path on the file system, we should run CI in a Windows environment in addition to running it on Linux-based environments.

While we're at it, we might as well also include MacOS.

@guusdk guusdk force-pushed the CI-include-Windows branch 2 times, most recently from 18be7b3 to 1611ca2 Compare August 21, 2025 09:49
@guusdk guusdk added backport 5.0 on merge, GHA will generate a PR with these changes against 5.0 branch backport 4.9 labels Aug 21, 2025
@guusdk guusdk force-pushed the CI-include-Windows branch 3 times, most recently from 3bab55e to 594df80 Compare August 21, 2025 13:42
@guusdk guusdk changed the title CI: also run on Windows CI: also run on Windows and MacOS Aug 21, 2025
@guusdk
Copy link
Member Author

guusdk commented Aug 21, 2025

I have added this as a way to detect issues as reported in and fixed by #2982

However, running the build on Windows and MacOS does not reproduce these issues (they can be reproduced by including a space character in the working directory - I've attempted to do that, but there doesn't seem to be an easy/maintainable way to do that in GitHub workflows - at least none that I can find).

With that, do we want to include Windows and MacOS as CI runners? They aren't exposing the issue that I had hoped, after all. With more runners, the chance of build failures because of flapping tests increases.

guusdk and others added 2 commits August 22, 2025 09:34
As we're producing binaries for Windows, and that OS notably differs from Linux in things like the representation of a path on the file system, we should run CI in a Windows environment in addition to running it on Linux-based environments.

While we're at it, we might as well also include MacOS.
@akrherz
Copy link
Member

akrherz commented Aug 22, 2025

MacOS failure filed as https://igniterealtime.atlassian.net/browse/OF-3119

@guusdk guusdk added backport 5.0 on merge, GHA will generate a PR with these changes against 5.0 branch and removed backport 5.0 on merge, GHA will generate a PR with these changes against 5.0 branch labels Oct 13, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

backport 5.0 on merge, GHA will generate a PR with these changes against 5.0 branch

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants