Second attempt at adding debugging messaging

[Whyborn]

First PR was failing due to existing files error, seeing if making a new PR gets over this problem.

---

🚀 The latest prerelease access-am3/pr19-7 at 67ec3de is here: #19 (comment) 🚀

[github-actions]

🚀 Attempted to deploy access-am3 Prerelease pr19-4 with commit f026d47

🖥️ Gadi Deployment ❌

[github-actions]

🚀 Attempted to deploy access-am3 Prerelease pr19-5 with commit 10620db

🖥️ Gadi Deployment ✔️

Usage Instructions

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

• 2025.12.000 as a Release (when merged).
• pr19-5 as a Prerelease (during this PR).

This Prerelease is accessible on Gadi using:

module use /g/data/vk83/prerelease/modules
module load access-am3/pr19-5

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/0.22/spack in the access-am3-pr19-5 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 0.22
• access-nri/spack-packages version 2025.09.004
• access-nri/spack-config version 2025.08.000

If the above was not what was expected, commit changes to config/versions.json in this PR.

[github-actions]

🚀 Attempted to deploy access-am3 Prerelease pr19-6 with commit de6bd22

🖥️ Gadi Deployment ✔️

Usage Instructions

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

• 2025.12.000 as a Release (when merged).
• pr19-6 as a Prerelease (during this PR).

This Prerelease is accessible on Gadi using:

module use /g/data/vk83/prerelease/modules
module load access-am3/pr19-6

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/0.22/spack in the access-am3-pr19-6 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 0.22
• access-nri/spack-packages version 2025.09.004
• access-nri/spack-config version 2025.08.000

If the above was not what was expected, commit changes to config/versions.json in this PR.

[github-actions]

🚀 Attempted to deploy access-am3 Prerelease pr19-7 with commit 67ec3de

🖥️ Gadi Deployment ✔️

Usage Instructions

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

• 2025.12.000 as a Release (when merged).
• pr19-7 as a Prerelease (during this PR).

This Prerelease is accessible on Gadi using:

module use /g/data/vk83/prerelease/modules
module load access-am3/pr19-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/0.22/spack in the access-am3-pr19-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 0.22
• access-nri/spack-packages version 2025.09.004
• access-nri/spack-config version 2025.08.000

If the above was not what was expected, commit changes to config/versions.json in this PR.