-
Notifications
You must be signed in to change notification settings - Fork 124
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
CI: add GitHub Actions check for Apple Silicon (M1) build #116
Comments
I can pick this up. Just to clarify we want to take advantage of the M1 runners to see if blazingmq builds via the darwin build script successfully? |
Hi @Sudo-Guy! That is correct, need to implement a check for the darwin build script using M1 or M2 (if available) GitHub Runner. |
Hi @Sudo-Guy! Do you plan working on this? |
I'll get around to it this weekend. A minor issue is that I need access to an ARM Mac machine right now, and free runners are unavailable. |
Thanks for the latest info @Sudo-Guy. Yes, indeed, they opened larger runners only, which are not free, on the 2nd of October, after this issue was opened. |
@Sudo-Guy it seems that it's not possible to use free M1/M2 runners right now. We discussed it and decided to wait until/if free Darwin runners are available. Could you add this workflow? |
Sure, sounds good. |
Might I make a suggestion? Feel free to use FlyCI's M1 and M2 runners. Our runners are on average 2x faster and 2x cheaper than GitHub's AND we have a free tier for OSS projects (see below). Install InstructrionsEasily replace your M1 runners: jobs:
ci:
- runs-on: macos-latest
+ runs-on: flyci-macos-large-latest-m1
steps:
- name: 👀 Checkout repo
uses: actions/checkout@v4 Or try the M2 runners: jobs:
ci:
- runs-on: macos-latest
+ runs-on: flyci-macos-large-latest-m2
steps:
- name: 👀 Checkout repo
uses: actions/checkout@v4 Pricing
500 mins/month Free for Public ReposIf your repo is public, then FlyCI offers 500 mins/month of free M1 runner usage with the Best Regards, |
Hi @kgantchev! Thank you for the suggestion. The proposed option is great for small open source projects. However, we have many developers who actively make changes in the repo. Some calculations. The free quota is 500 min, consider M1/M2 runner time 20 min for each CI launch. With these assumptions, the quota will be exceeded after ~25 CI launches. This means:
In conclusion, weekly checks could be performed, which could be good enough for us. I will discuss it with the team. |
|
Hi @syuzvinsky, could you do this when you have time? |
For reference, this is how memray has done it. |
Is there an existing proposal for this?
Is your feature request related to a problem?
We don't have automatic checks for M1/M2 builds.
Describe the solution you'd like
According to this roadmap, Apple Silicon (M1) is in public beta in GitHub Actions:
github/roadmap#528
Might be possible to use the corresponding runner to check darwin build script automatically.
Alternatives you considered
No response
The text was updated successfully, but these errors were encountered: