Do not move micromamba cache to %MINIFORGE_HOME%
#2107
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
jaimergp
added a commit
to h-vetinari/arrow-cpp-feedstock
that referenced
this pull request
Oct 29, 2024
MNT: Re-rendered with conda-build 24.9.0, conda-smithy 3.43.1.dev12+g92312b51, and conda-forge-pinning 2024.10.29.12.41.35
|
Tested at conda-forge/arrow-cpp-feedstock@ |
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.
Checklist
newsentrypython conda_smithy/schema.py)Patches symptom behind #2101, but at the cost of not reusing the micromamba cache for conda-build on Windows. It should have a minor impact in the timings, given how fast the CI download is anyway. The mamba team has been notified of the issue and will be looking into it, so we can revert the workaround in the future, once fixed.