-
-
Notifications
You must be signed in to change notification settings - Fork 25.8k
CI Bump macOS version to 13 on Azure #30169
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
Conversation
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 if it goes through.
Maybe we can try to merge this to see if this has any impact on the stalled jobs? It's easy to revert in case we need to. |
Looks like Azure CI jobs are running again at least in this PR 🎉 but not #30167 apparently 😅. For completeness, conda-forge has seen the same issue of Azure CI not being triggered conda-forge/status#188 and there is now an acknowledged Azure Devops incident https://status.dev.azure.com/_event/559260722. So hopefully this should be fixed for real in the not so distant future. |
Ah after reading your Discord message, I guessed you did manually trigger the Azure build |
Yes I did sorry... |
The |
I'm reading this thread that is related: actions/runner-images#9262 |
So indeed, it seems that the way to go is to install |
A subsequent question now is about the type of CPU on those machines? On GitHub action We can easily make the script adaptable to download the right archive though. |
I open the following PR against this branch: lesteve#39 I open this PR to see if it works and apparently, it worked almost :): #30185 While the install of |
Closing in favour of #30185 |
See actions/runner-images#10721. macOS-12 removal on Azure is scheduled for December 2024, brownout windows will start in November 2024.