TEST: Final SDR Test for Spack v1

[CodeGat]

Testing for ACCESS-NRI/build-cd#326

---

🚀 The latest prerelease gh/pr21-9 at e378525 is here: #21 (comment) 🚀

[github-actions]

🚀 Attempted to deploy gh Prerelease pr21-1 with commit 532f9f2

🖥️ Gadi Deployment ❌

[github-actions]

🚀 Attempted to deploy gh Prerelease pr21-2 with commit 0bf75fd

🖥️ Gadi Deployment ❌

[github-actions]

🚀 Attempted to deploy gh Prerelease pr21-2 with commit 231cf02

🖥️ Gadi Deployment ✔️

Usage Instructions

gh, defined in gh/spack.yaml, will be deployed to Gadi as:

• 2.49.2-1 as a Release (when merged).
• pr21-2 as a Prerelease (during this PR).

This Prerelease is accessible on Gadi using:

module use /g/data/vk83/prerelease/modules
module load gh/pr21-2

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 gh-pr21-2 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:

• access-nri/spack on branch 1.1
• spack/spack-packages version 8ed34337e15d759890b68682d704aa55dd243537
• access-nri/access-spack-packages version 2025.06.001
• access-nri/spack-config version development-gadi

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.

[CodeGat]

!redeploy

[github-actions]

🚀 Attempted to deploy gh Prerelease pr21-3 with commit 231cf02

🖥️ Gadi Deployment ❌

[CodeGat]

!redeploy

TC 2.2
(After main did not contain the required workflow updates)

[github-actions]

🚀 Attempted to deploy gh Prerelease pr21-4 with commit 231cf02

🖥️ Gadi Deployment ✔️

Usage Instructions

gh, defined in gh/spack.yaml, will be deployed to Gadi as:

• 2.49.2-1 as a Release (when merged).
• pr21-4 as a Prerelease (during this PR).

This Prerelease is accessible on Gadi using:

module use /g/data/vk83/prerelease/modules
module load gh/pr21-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 gh-pr21-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:

• access-nri/spack on branch 1.1
• spack/spack-packages version 8ed34337e15d759890b68682d704aa55dd243537
• access-nri/access-spack-packages version 2025.06.001
• access-nri/spack-config version development-gadi

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.

[github-actions]

🚀 Attempted to deploy gh Prerelease pr21-9 with commit e378525

🖥️ Gadi Deployment ✔️

Usage Instructions

gh, defined in gh/spack.yaml, will be deployed to Gadi as:

• 2.49.2-1 as a Release (when merged).
• pr21-9 as a Prerelease (during this PR).

This Prerelease is accessible on Gadi using:

module use /g/data/vk83/prerelease/modules
module load gh/pr21-9

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 gh-pr21-9 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:

• access-nri/spack on branch 1.1
• spack/spack-packages version 8ed34337e15d759890b68682d704aa55dd243537
• access-nri/access-spack-packages version 2025.06.001
• access-nri/spack-config version development-gadi

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.