TEST: Final MDR Test of Spack V1.X Migration

[CodeGat]

Test cases defined in ACCESS-NRI/build-cd#326 (Testing > MDRs)

---

🚀 The latest prerelease access-test/pr63-9 at eac6874 is here: #63 (comment) 🚀

[github-actions]

🚀 Attempted to deploy access-test Prerelease pr63-1 with commit 31ee5d6

🖥️ Gadi Deployment ✔️

Usage Instructions

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

• 2026.01.000 as a Release (when merged).
• pr63-1 as a Prerelease (during this PR).

This Prerelease is accessible on Gadi using:

module use /g/data/vk83/prerelease/modules
module load access-test/pr63-1

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-test-pr63-1 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 api-v2
• access-nri/spack-config version 2025.11.003

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 access-test Prerelease pr63-2 with commit 5721f45

🖥️ Gadi Deployment ✔️

Usage Instructions

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

• 2025.09.000 as a Release (when merged).
• pr63-2 as a Prerelease (during this PR).

This Prerelease is accessible on Gadi using:

module use /g/data/vk83/prerelease/modules
module load access-test/pr63-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 access-test-pr63-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 api-v2
• access-nri/spack-config version 2025.11.003

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 access-test Prerelease pr63-5 with commit 357a4cf

🖥️ Gadi Deployment ❌

[github-actions]

🚀 Attempted to deploy access-test Prerelease pr63-4 with commit 5721f45

🖥️ Gadi Deployment ✔️

Usage Instructions

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

• 2025.09.000 as a Release (when merged).
• pr63-4 as a Prerelease (during this PR).

This Prerelease is accessible on Gadi using:

module use /g/data/vk83/prerelease/modules
module load access-test/pr63-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-test-pr63-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 api-v2
• access-nri/spack-config version 2025.11.003

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 access-test Prerelease pr63-6 with commit 56fe84d

🖥️ Gadi Deployment ❌

[github-actions]

🚀 Attempted to deploy access-test Prerelease pr63-7 with commit 3e9c06f

🖥️ Gadi Deployment ✔️

Usage Instructions

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

• 2026.01.000 as a Release (when merged).
• pr63-7 as a Prerelease (during this PR).

This Prerelease is accessible on Gadi using:

module use /g/data/vk83/prerelease/modules
module load access-test/pr63-7

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-test-pr63-7 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 api-v2
• access-nri/spack-config version 2025.11.003

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 access-test Prerelease pr63-8 with commit 3e9c06f

🖥️ Gadi Deployment ✔️

Usage Instructions

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

• 2026.01.000 as a Release (when merged).
• pr63-8 as a Prerelease (during this PR).

This Prerelease is accessible on Gadi using:

module use /g/data/vk83/prerelease/modules
module load access-test/pr63-8

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-test-pr63-8 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 api-v2
• access-nri/spack-config version 2025.11.003

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 access-test Prerelease pr63-9 with commit eac6874

🖥️ Gadi Deployment ✔️

Usage Instructions

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

• 2026.01.000 as a Release (when merged).
• pr63-9 as a Prerelease (during this PR).

This Prerelease is accessible on Gadi using:

module use /g/data/vk83/prerelease/modules
module load access-test/pr63-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 access-test-pr63-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 api-v2
• access-nri/spack-config version 2025.11.003

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.