Release candidate - 2026.03.000

[anton-seaice]

This change:

• updates upstream components (closes Upstream model component update, tweaking the docs #174 and contributes to Upstream model component update: January 2026. access-om3-configs#1028)
• sets target to x86_64_v4 (closes Update target #200)
• adds debug flags and -grecord-gcc-switches for main components (closes Debug builds broken #94 and closes Stack trace information missing #13 and closes Set -grecord-gcc-switches #199)

---

🚀 The latest prerelease access-om3/pr209-2 at 12e01ad is here: #209 (comment) 🚀

---

🚀 The latest prerelease access-om3/pr209-7 at bb18a6a is here: #209 (comment) 🚀

[github-actions]

🚀 Attempted to deploy access-om3 Prerelease pr209-1 with commit aa20d46

🖥️ Gadi Deployment ✔️

Usage Instructions

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

• 2025.08.002 as a Release (when merged).
• pr209-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/pr209-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-pr209-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 383e969358c951abe17623696083e6f862c4488e
• access-nri/access-spack-packages version 2026.02.002
• access-nri/spack-config version 2026.02.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-om3 Prerelease pr209-2 with commit 12e01ad

🖥️ Gadi Deployment ✔️

Usage Instructions

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

• 2025.08.002 as a Release (when merged).
• pr209-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/pr209-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-pr209-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 383e969358c951abe17623696083e6f862c4488e
• access-nri/access-spack-packages version 2026.02.002
• access-nri/spack-config version 2026.02.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.

[anton-seaice]

!update-configs

[github-actions]

🔧 Opening/Updating Model Configuration PRs in ACCESS-NRI/access-om3-configs

Configurations Requested

Configurations requested from profile default:

• dev-MC_100km_jra_ryf

• dev-MC_100km_jra_ryf+wombatlite

• dev-MC_25km_jra_ryf

Pull Requests Opened/Updated

The following PRs were opened/updated:

• Auto update dev-MC_100km_jra_ryf to use access-om3/pr209-2 access-om3-configs#1219

• Auto update dev-MC_100km_jra_ryf+wombatlite to use access-om3/pr209-2 access-om3-configs#1217

• Auto update dev-MC_25km_jra_ryf to use access-om3/pr209-2 access-om3-configs#1218

More details can be found in the workflow run: https://github.com/ACCESS-NRI/ACCESS-OM3/actions/runs/23124751329

[github-actions]

🚀 Attempted to deploy access-om3 Prerelease pr209-3 with commit a2a7fa2

🖥️ Gadi Deployment ✔️

Usage Instructions

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

• 2025.08.002 as a Release (when merged).
• pr209-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/pr209-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-pr209-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
• spack/spack-packages version 383e969358c951abe17623696083e6f862c4488e
• access-nri/access-spack-packages version om3-2026.03-update
• access-nri/spack-config version 2026.02.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.

[anton-seaice]

Up to pr209-3 is not answer changing - see ACCESS-NRI/access-om3-configs#1219 (comment)

The rest of the changes will be answer changing

Trying this in the debugger from the PR build, it's missing source code. doing a local build and spack install --keep-stage makes the source code available too

[github-actions]

🚀 Attempted to deploy access-om3 Prerelease pr209-4 with commit acb1025

🖥️ Gadi Deployment ❌

[github-actions]

🚀 Attempted to deploy access-om3 Prerelease pr209-5 with commit 050d00e

🖥️ Gadi Deployment ❌

[anton-seaice]

!redeploy

[anton-seaice]

@CodeGat - it seems like if two jobs try and install the same package at the same time they always conflict:

e.g. from the above two builds which were running concurrently

https://github.com/ACCESS-NRI/ACCESS-OM3/actions/runs/23127192367/job/67172796218#step:15:2692

https://github.com/ACCESS-NRI/ACCESS-OM3/actions/runs/23127472124/job/67173612949#step:15:2493

[CodeGat]

Ah, so fms concretized to the same hash in both, both tried to build it, and then they both failed? That might be quite a hard one to fix...there should be database locks that prevent that, if they're both attempting to write to that directory at the same time 😬 Has that happened before?

[anton-seaice]

Yeah i've done it several times.

It's kind of accidental mostly ... push a commit, forget something, quickly push a second commit and then you end up with two builds of very similar things. (Or the other one is push a commit, and change PR status in quick succession)

[github-actions]

🚀 Attempted to deploy access-om3 Prerelease pr209-6 with commit 050d00e

🖥️ Gadi Deployment ✔️

Usage Instructions

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

• 2025.08.002 as a Release (when merged).
• pr209-6 as a Prerelease (during this PR).

This Prerelease is accessible on Gadi using:

module use /g/data/vk83/prerelease/modules
module load access-om3/pr209-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/1.1/spack in the access-om3-pr209-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 1.1
• spack/spack-packages version 383e969358c951abe17623696083e6f862c4488e
• access-nri/access-spack-packages version om3-2026.03-update
• access-nri/spack-config version 2026.02.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-om3 Prerelease pr209-7 with commit bb18a6a

🖥️ Gadi Deployment ❌