analyzer
analyzer copied to clipboard
Investigate CI for MacOS on M1 machines
It seems like Cirrus CI (which has unlimited free minutes for OpenSource projects) might have support here. Might make sense to set this up for the MacOS builds, even if it means our CI will be spread between services.
https://cirrus-ci.org/guide/macOS/
There's also this from some months ago: https://github.com/github/roadmap/issues/528. The beta does not appear to be public though.
Just having the CI wouldn't be very useful though, because it doesn't help much with debugging the issue in the first place. As long as #824 is still open, such CI would always fail, which isn't a surprise.
Also, #824 isn't even specific to M1, but just arm64 in general. If we really wanted to fix it, then it should be possible under qemu.
The M1 Github runners are now publicly available: https://github.blog/2023-10-02-introducing-the-new-apple-silicon-powered-m1-macos-larger-runner-for-github-actions/
I think in the long run the number of people using M1 Mac's (as opposed to the Intel ones where Goblint just works) is only gonna keep increasing. Might make sense to include M1 workflows in the unlocked runs (even if we have to exclude some of the tests from there for now).
https://github.blog/changelog/2024-01-30-github-actions-introducing-the-new-m1-macos-runner-available-to-open-source/ and now they're free!