Move to mambaorg/micromamba as docker base image for CI #276
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
sblauth
added
bug
sblauth
changed the title
|
Note, that the tests which are currently running, can only fail. (They are using the "old" docker image). However, new ones are only built after the PR is merged. Therefore, this PR will get force-merged to main |
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.
This PR fixes an issue with the docker builds we have been experiencing the last couple of weeks. It comes from a compatibility issue between conda and mamba (when mixing default and conda-forge channels).
In this PR, a new docker image is used to define the "quick" tests, that run on every push (mambaorg/micromamba:1-jammy, so ubuntu).
This fixes the issue of the tests and the failing CI workflows