Update remote temp spack manifest name to prevent ambiguity #253
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.
See ACCESS-NRI/ACCESS-OM3#64, specifically ACCESS-NRI/ACCESS-OM3#64 (comment)
Background
When a large amount of prereleases from the same repository are created around the same time, there is a possibility of the remote, temporarily stored
MODEL.spack.yaml
to be overwritten before thespack env create
call.The PR
In this PR:
access-om3-82974392347.spack.yaml
, rather than justaccess-om3.spack.yaml