You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
we should have a QA configuration check that compares the executable paths in manifests/exe.yaml and check they match an install path in the spack.locations.json release artefact for the relevant model version
Once we have the ability to utilise
module load model/version
inpayu
configurations#10
we should have a QA configuration check that compares the executable paths in
manifests/exe.yaml
and check they match an install path in thespack.locations.json
release artefact for the relevant model versionACCESS-NRI/build-cd#51
The release is available at a predictable URL for a given model version, e.g.
https://github.com/ACCESS-NRI/ACCESS-OM2/releases/tag/2024.03.0
and the relevant artefact is just a path added to that url, e.g.
https://github.com/ACCESS-NRI/ACCESS-OM2/releases/download/2024.03.0/spack.location
(note that
spack.location.json
was not generated for the above release, but will be available in the future)The text was updated successfully, but these errors were encountered: