CM3 rofi spreading test

[kieranricardo]

Test build for ACCESS-NRI/CMEPS#23 and

---

🚀 The latest prerelease access-om3/pr248-3 at a39ebeb is here: #248 (comment) 🚀

[github-actions]

🚀 Attempted to deploy access-om3 Prerelease pr248-1 with commit f110486

🖥️ Gadi Deployment ✔️

Usage Instructions

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

• 2025.08.999 as a Release (when merged).
• pr248-1 as a Prerelease (during this PR).

This Prerelease is accessible on Gadi using:

module use /g/data/vk83/prerelease/modules
module load access-om3/pr248-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-om3-pr248-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
• ACCESS-NRI/upstream-spack-packages version access/v1.1
• access-nri/access-spack-packages version 2026.06.000
• access-nri/spack-config version 2026.05.004

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-om3 Prerelease pr248-2 with commit d55234d

🖥️ Gadi Deployment ❌

[github-actions]

🚀 Attempted to deploy access-om3 Prerelease pr248-2 with commit 2878231

🖥️ Gadi Deployment ✔️

Usage Instructions

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

• 2026.05.003 as a Release (when merged).
• pr248-2 as a Prerelease (during this PR).

This Prerelease is accessible on Gadi using:

module use /g/data/vk83/prerelease/modules
module load access-om3/pr248-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-om3-pr248-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
• ACCESS-NRI/upstream-spack-packages version access/v1.1
• access-nri/access-spack-packages version 2026.08.005
• access-nri/spack-config version 2026.07.001

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-om3 Prerelease pr248-3 with commit a39ebeb

🖥️ Gadi Deployment ✔️

Usage Instructions

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

• 2026.05.003 as a Release (when merged).
• pr248-3 as a Prerelease (during this PR).

This Prerelease is accessible on Gadi using:

module use /g/data/vk83/prerelease/modules
module load access-om3/pr248-3

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-om3-pr248-3 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
• ACCESS-NRI/upstream-spack-packages version access/v1.1
• access-nri/access-spack-packages version 2026.08.005
• access-nri/spack-config version 2026.08.001

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