-
Notifications
You must be signed in to change notification settings - Fork 81
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
macOS CI fixes #188
macOS CI fixes #188
Conversation
Current nixpkgs doesn't support macOS Big Sur (11). Its support landed in nixpkgs in 21.11, but that also broke support for Catalina (10.15), so switch CI workflow to use "macos-11" runner. Fixes #175
On CI we set NIX_PATH to "nixpkgs=./nixpkgs.nix", so nix-shell tries to use it from within the example's directory and fails, it tries to use builtin bash. On macOS it is too old, so we should make sure that the one from nixpkgs is used. Related to #176
For some reason GitHub expects build that is removed in this PR (the |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Great work on pinning the issues with macOS!
However I would really like to avoid making the test execution script a highly nested, if-else driven construct – I have given a suggestion in review, but I do not mind any solution ;)
b206f91
to
5110ff1
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
This was a branch protection setting. I've changed it to point to macos-11 |
Thank you @YorikSar for fixing this! |
macos-11
builder testsmacos-11
builder for examples, excluding Python and Rust ones (see Python example tries to run as bash script on macOS #186 and Rust example fails to compile on macOS because of libiconv #187)This should close #175 and #176.