feat(ci): Remove defaults channel from conda setup and use strict channel prio #1554
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
…nnel prio With the default settings the generated pinned environments may still contain references to the defaults channel in certain cases (currently to zstandard), and the test workflow does not fail because it also falls back to the defaults channel.
coroa
force-pushed
the
feat/remove-defaults-from-conda-environments
branch
from
67d3016 to
676b3b8
Compare
Avoids dependencies on proprietary anaconda pkgs channels
|
Success 🤡 https://github.com/PyPSA/pypsa-eur/actions/runs/13530573076/job/37811548433#step:10:21 failed with the desired |
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.
With the default settings the generated pinned environments may still contain references to the defaults channel in certain cases (currently to zstandard), and the test workflow does not fail because it also falls back to the defaults channel.
Was able to reproduce locally the creation of a locked environment with conda
which could not be installed by mamba (unless the defaults channel was explicitly
configured). Ensuring the defaults channel does not appear in
~/.condarcisenough to create locked environments which work with my current mamba setup.
Strict channel priority should improve the situation further.