-
-
Notifications
You must be signed in to change notification settings - Fork 18.2k
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: fix wrong syntax in CI env yml files (mamba 2.0 compat) #59910
Conversation
It seems like there a few issues with mamba 2.0 with windows (mamba-org/setup-micromamba#227) and the We may just need to pin the mamba version |
I opened #59912 - planning to merge as soon as that's green. We can then use this to unpin once upstream is fixed. |
This pull request is stale because it has been open for thirty days with no activity. Please update and respond to this comment if you're still interested in working on this. |
Thanks @jorisvandenbossche |
Owee, I'm MrMeeseeks, Look at me. There seem to be a conflict, please backport manually. Here are approximate instructions:
And apply the correct labels and milestones. Congratulations — you did some good work! Hopefully your backport PR will be tested by the continuous integration and merged soon! Remember to remove the If these instructions are inaccurate, feel free to suggest an improvement. |
Manual backport -> #60175 |
All CI is failing with the new mamba 2.0 release. But it seems this is because we had invalid syntax (pip extras syntax) in our environment files, where mamba now fails on (previously used conda for parsing the yml files).