Silence warnings about non-existent index for mirrors that don't have and don't need a buildcache index#575
Merged
climbfuji merged 2 commits intoJCSDA:spack-stack-devfrom Feb 3, 2026
Conversation
…istent index for mirrors, because this warning is issued for all mirrors (source, bootstrap, ...)
96ad721 to
5b7f3a3
Compare
… feature/no_errors_as_warnings_for_nonexistent_buildcache_index
Collaborator
|
@climbfuji Is this related to the: things I get? |
Collaborator
Author
Exactly. These get silenced by the PR. |
AlexanderRichert-NOAA
approved these changes
Feb 3, 2026
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
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.
Description
lib/spack/spack/binary_distribution.py: silence warnings about non-existent index for mirrors, because this warning is issued for all mirrors (source, bootstrap, ...), even if they don't have or don't need a build cache index to function correctly. See comments from Spack developers just below my changes.These warnings look like legitimate errors, clutter the output of automated build/deploy systems, and confuse users and developers.
I do not indent to send this upstream but maintain the diff in our fork/branch.
Testing
See JCSDA/spack-stack#1896