Concurrent Package Installation for ci using spack v1.0#73
Draft
Concurrent Package Installation for ci using spack v1.0#73
ci using spack v1.0#73Conversation
CodeGat
changed the title
ci-upstream using spack v1.0ci using spack v1.0
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.
Background
Building the upstream image takes an exceptionally long time. Luckily
spack v1.0allows concurrent installation of packages, which offers a significant speedup.This PR is used to test out both the self-hosted and GitHub-hosted variants of the CI.
For the GitHub-hosted variant, this update should be uncontroversial, but the self-hosted variant must be mindful of the kuberenetes node resources - test this.
The PR
Testing
Add when done!