Speed up conda environment creation #804
Merged
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
Conda's opaque package resolution scheme causes us to have extremely long environment solves, followed by getting an ancient version of FiPy. We want *new* fipy, and can accept an old gmsh, but how to tell conda that?
guyer
changed the title
|
Remaining failures are unrelated to this PR: |
Closed
|
Well done finding Mamba. Seems better for a package manager to be Python independent. Maybe start rebasing this sort of pull request with a few or single good commit message. |
wd15
approved these changes
Apr 24, 2021
|
@wd15 Thanks. The developer actually pointed me at it awhile ago when the conda solver was coming up with insane results, but I was reminded of it here when I went tracking down some bookmarks I had on speeding things up. I always squash and merge these PRs because the troubleshooting history is irrelevant. For more complicated PRs, I rebase and submit a new PR once everything is working. People have requested that GitHub enable rebasing of PRs, but that's fallen on deaf ears so far. |
guyer
deleted the
issue800-CircleCI_conda2_env_is_really_slow_and_ends_up_installing_FiPy_3_3
branch
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.
Conda's opaque package resolution scheme causes us to have
extremely long environment solves, followed by getting an
ancient version of FiPy.
We want new fipy, and can accept an old gmsh,
but how to tell conda that?
Fixes #800