Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Check executable paths match those deployed for specified model version #18

Closed
aidanheerdegen opened this issue May 3, 2024 · 0 comments · Fixed by #30
Closed

Check executable paths match those deployed for specified model version #18

aidanheerdegen opened this issue May 3, 2024 · 0 comments · Fixed by #30
Assignees
Labels
priority:high type:config Model configurations type:qa-check Quality Assurance Checks

Comments

@aidanheerdegen
Copy link
Member

Once we have the ability to utilise module load model/version in payu 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 the spack.locations.json release artefact for the relevant model version

ACCESS-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)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
priority:high type:config Model configurations type:qa-check Quality Assurance Checks
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants