debug conda nightlies build #664
Closed
Conversation
This file contains hidden or 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
The builds are failing for `aarch64`, and one log message hints that concurrent builds are messing with the same cache. Ref: apache#659
The `actual` sha256 hashes match both what I calculate by downloading and running `sha256sum` and what is posted on conda-forge. I suspect then that our build is using some bad cached value as the "expected". conda-forge: https://conda.anaconda.org/conda-forge/noarch/ Ref: apache#659
Michael-J-Ward
force-pushed
the
debug-conda-build
branch
from
7813897 to
51d5ad0
Compare
Cleaning out the cache caused all the conda builds to break, instead of just the `aarch64` ones. This commit reverts back to original CI def.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Which issue does this PR close?
Closes #659 (hopefully)
Rationale for this change
What changes are included in this PR?
Are there any user-facing changes?
No