Skip to content

Test Updated Metadata Fix#30

Draft
CodeGat wants to merge 14 commits intomainfrom
infra-update-v8-check-meta-upload
Draft

Test Updated Metadata Fix#30
CodeGat wants to merge 14 commits intomainfrom
infra-update-v8-check-meta-upload

Conversation

@CodeGat
Copy link
Member

@CodeGat CodeGat commented Mar 20, 2026

  • [no ci] infra: Update to v8
  • [no ci] infra: Update spack version to v1.1, update manifest schema to 2-0-0
  • [no ci] spack.yaml: Dedent list elements for spack-style manifests
  • [no ci] spack.yaml: Add reserved definitions
  • [no ci] spack.yaml: Use toolchains
  • [no ci] versions.json,spack.yaml: Add ukmo-restricted-scope to custom-scopes rather than environment
  • [no ci] Remove inputs.pr, updated versions in ci-comment
  • [no ci] Update config/versions.json access-spack-packages version to common api-v2 tag
  • TEST: Update branch to test-v8
  • Update to language-based compiler restrictions
  • Update access-spack-packages to 2026.03.004 (fixes fiat@um missing patch bug)
  • TEST: metadata fix
  • Redeploy after skip of base manifest check

🚀 The latest prerelease access-am3/pr30-4 at 9e6b36d is here: #30 (comment) 🚀

@CodeGat CodeGat self-assigned this Mar 20, 2026
@github-actions
Copy link

🚀 Attempted to deploy access-am3 Prerelease pr30-3 with commit eaf7969

🖥️ Gadi Deployment ❌

@github-actions
Copy link

🚀 Attempted to deploy access-am3 Prerelease pr30-4 with commit 9e6b36d

🖥️ Gadi Deployment ✔️

Usage Instructions

access-am3, defined in spack.yaml, will be deployed to Gadi as:

  • 2026.02.000 as a Release (when merged).
  • pr30-4 as a Prerelease (during this PR).

This Prerelease is accessible on Gadi using:

module use /g/data/vk83/prerelease/modules
module load access-am3/pr30-4

When using the above modules, the binaries shall be on your $PATH.

For advanced users, this Prerelease is also accessible on Gadi via /g/data/vk83/prerelease/apps/spack/1.1/spack in the access-am3-pr30-4 environment.
Due to inode-saving measures, one will have to manually untar the environment metadata before environment activation with tar -xf .spack-env .spack-env.tar. It will require one to have write privileges.

Configuration Information

This Prerelease is deployed using:

If the above was not what was expected, commit changes to config/versions.json in this PR, or propose changes to build-cds config/settings.json.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant