Workaround for setup-miniconda failing to install mamba on ubuntu #506
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…failures in mamba installation during setup.
|
@pvanheus I think you were the original author of .github/workflows/pangolin.yml a couple years ago including the |
|
If I don't hear any objections in the next day I'll just merge this. 🙂 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
pangolin github action tests have been failing on ubuntu for about a week now (?) not because of anything in pangolin, but because the conda-incubator/setup-miniconda action's conda command to install mamba fails with a ton of cryptic conflict errors. I found that removing
mamba-version: "*"from pangolin.yml would prevent the crash, but it would be nice to keep mamba in the CI too. I found a nice report of this issue, including suggested workarounds: conda-incubator/setup-miniconda#274 and indeed the first suggested workaround (replacingmamba-version: "*"withminiforge-variant: Mambaforge) worked.