ci: add spack lockfiles and drop dead setup-spack ref#548
Draft
dennisklein wants to merge 2 commits into
Draft
Conversation
- generated on ubuntu-24.04 by buildcache run 26721959759 - one lock per (env, gcc): latest gcc 12/13/14/15 and boost187 gcc15
setup-spack@v3 renamed ref to spack_ref, so the old ref input was silently ignored (and emitted a warning each run) while spack ran on its develop default anyway. - remove the dead ref input from the setup-deps action and the update-index job
Member
Author
|
Holding as draft. CI investigation shows the committed lockfiles pin gcc as a host-path Root cause is broader: gcc is compiled from source (~58 min) on every buildcache run and never pushed (externals are excluded from |
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
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.
Follow-up to #547.
test/ci/locks/<env>-gcc<N>.lockfiles (generated on ubuntu-24.04 by buildcache run 26721959759) so CI installs from a fixed concretization instead of re-solvingrefinput fromsetup-spack@v3in the setup-deps action and the update-index job: v3 renamed it tospack_ref, so it was silently ignored and emitted a warning each run