WIP: Replace conda install with pip due to unreliable libmamba-solver [skip ci] #11506
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
We started suffering from internal docker build error after mamba released 2.0 https://github.com/mamba-org/mamba/releases/tag/2024.09.25 which is now the default solver of conda for python 3.10+
and failed
This change was trying to apply a workaround to use classic solver (this would significantly increase the conda install time, from ~10mins to ~50-70mins). this is too slow, so I starts trying to make IT to run with pip installed cudf