-
-
Notifications
You must be signed in to change notification settings - Fork 18.6k
CI: Fix slow mamba solver issue by limiting boto3 versions #61594
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
base: main
Are you sure you want to change the base?
Conversation
This doesn't seem to work. Removing |
The dependencies for Not too sure if the problem is really with |
Based on my tests, this is what makes the solver happy. Relaxing the conditions causes the very slow mamba install times. This breaks the check for minimum versions, so it can't be merged as is (and I'll add a comment when we decide what to do). @mroeschke not sure if you have an opinion on what to do to avoid the mamba problems based on this. Not too sure what's going on. |
I'm curious if conda's libmamba solver has the same issue. Potentially based on conda/conda-libmamba-solver#668 it may. (It's on my radar to maybe switch to https://github.com/conda-incubator/setup-miniconda given that mamba activity is kinda slow as you mentioned) It's a shame we have to pin, but I'm OK with it to speed up solve times |
I had the impression that conda, mamba, micromamba and pixi all use libmamba, so not sure if changing tool would be helpful. But I'm not so sure about the exact details. |
Closes #61531
Probably better to rerun the CI 3 or 4 times to be sure this is the problem and the solution. But based on local tests, seems like boto3 has a huge number of versions (they release almost every day), and that's the problem with the mamba solver. Limiting the number of versions provided to the solver should help. 1.27 is from 2 years ago, consistent with other packages. Why only fails for 3.13? No idea