-
Notifications
You must be signed in to change notification settings - Fork 173
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
Make CI for self-hosted M1 a little more reproducible #1636
Comments
Worth keeping an eye on actions/runner-images#2187 which is downstream of github/roadmap#528 also as if they add support upstream, that'll be easier than self-hosted alternatives Currently marked as:
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
We currently do tests of m1 builds by running self-hosted runners on m1 machines (e.g. my laptop).
I had to do this recently, and here were the steps I did to get it working:
m1
tag thoughbrew install [email protected]
), and then make sure/opt/homebrew/opt/[email protected]/bin/python3
exists, i had tosymlink
for 3.8 and 3.9brew install [email protected]
), and then symlink the binaries to~/go/bin/go1.16
etc.The text was updated successfully, but these errors were encountered: