Build with optimisation set in SPR, and with the bug-fix from Martin by manodeep · Pull Request #193 · ACCESS-NRI/ACCESS-ESM1.6

manodeep · 2026-03-04T11:18:57Z

Using an updated UM7 SPR that sets -O2 for atm_step and u_model, and keeps -O0 for set_atm_pointers + building UM7 with the bug-fix from Martin (that fixes the wrong offsets which were unveiled by my setting the -O2 flags across all three top-level UM7 routines)

🚀 The latest prerelease access-esm1p6/pr193-10 at 82e41f9 is here: #193 (comment) 🚀

github-actions · 2026-03-04T11:19:39Z

The model version in the spack.yaml has not been updated.
You can update it manually.
Alternatively, comment the following to have it updated and committed automatically:

!bump major for feature releases
!bump minor for bugfixes

github-actions · 2026-03-04T11:21:30Z

🚀 Attempted to deploy access-esm1p6 Prerelease pr193-1 with commit 0cd6217

🖥️ `Gadi` Deployment ❌

github-actions · 2026-03-04T11:28:48Z

🚀 Attempted to deploy access-esm1p6 Prerelease pr193-1 with commit 0cd6217

🖥️ `Gadi` Deployment ❌

github-actions · 2026-03-04T12:00:23Z

🚀 Attempted to deploy access-esm1p6 Prerelease pr193-2 with commit 2abe560

🖥️ `Gadi` Deployment ✔️

Usage Instructions

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

2026.02.001 as a Release (when merged).
pr193-2 as a Prerelease (during this PR).

This Prerelease is accessible on Gadi using:

module use /g/data/vk83/prerelease/modules
module load access-esm1p6/pr193-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-esm1p6-pr193-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 0b247731bdb7180bfaf1f51d3f9aeaf22a4e2b55
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.

manodeep · 2026-03-04T12:09:47Z

!update-configs

github-actions · 2026-03-04T12:11:14Z

🔧 Opening/Updating Model Configuration PRs in ACCESS-NRI/access-esm1.6-configs

Configurations Requested

Configurations requested from profile default:

dev-1pctCO2
dev-4xCO2+concentrations
dev-historical+concentrations
dev-preindustrial+concentrations

Pull Requests Opened/Updated

The following PRs were opened/updated:

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

…sm1p6

manodeep · 2026-03-05T23:05:37Z

!redeploy

github-actions · 2026-03-05T23:32:34Z

🚀 Attempted to deploy access-esm1p6 Prerelease pr193-4 with commit 81c460c

🖥️ `Gadi` Deployment ❌

github-actions · 2026-03-05T23:37:12Z

🚀 Attempted to deploy access-esm1p6 Prerelease pr193-3 with commit 81c460c

🖥️ `Gadi` Deployment ❌

manodeep · 2026-03-05T23:57:05Z

Whoops - I might have set off a race condition by manually specifying redeploy (which I did because there was no indication that a new deploy was starting)

manodeep · 2026-03-05T23:57:14Z

!redeploy

github-actions · 2026-03-06T00:12:02Z

🚀 Attempted to deploy access-esm1p6 Prerelease pr193-5 with commit 81c460c

🖥️ `Gadi` Deployment ✔️

Usage Instructions

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

2026.02.001 as a Release (when merged).
pr193-5 as a Prerelease (during this PR).

This Prerelease is accessible on Gadi using:

module use /g/data/vk83/prerelease/modules
module load access-esm1p6/pr193-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/1.1/spack in the access-esm1p6-pr193-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 1.1
spack/spack-packages version 383e969358c951abe17623696083e6f862c4488e
access-nri/access-spack-packages version 0b247731bdb7180bfaf1f51d3f9aeaf22a4e2b55
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.

manodeep · 2026-03-06T00:12:27Z

!update-configs

github-actions · 2026-03-06T00:13:36Z

🔧 Opening/Updating Model Configuration PRs in ACCESS-NRI/access-esm1.6-configs

Configurations Requested

Configurations requested from profile default:

dev-1pctCO2
dev-4xCO2+concentrations
dev-historical+concentrations
dev-preindustrial+concentrations

Pull Requests Opened/Updated

The following PRs were opened/updated:

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

github-actions · 2026-03-06T04:14:23Z

🚀 Attempted to deploy access-esm1p6 Prerelease pr193-6 with commit 6c25bc1

🖥️ `Gadi` Deployment ✔️

Usage Instructions

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

2026.02.001 as a Release (when merged).
pr193-6 as a Prerelease (during this PR).

This Prerelease is accessible on Gadi using:

module use /g/data/vk83/prerelease/modules
module load access-esm1p6/pr193-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-esm1p6-pr193-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 0b247731bdb7180bfaf1f51d3f9aeaf22a4e2b55
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 · 2026-03-06T06:46:05Z

🚀 Attempted to deploy access-esm1p6 Prerelease pr193-7 with commit a4bfaa8

🖥️ `Gadi` Deployment ❌

manodeep · 2026-03-06T06:49:03Z

Sorry for another ping @CodeGat - think we have seen this new prefix is too big error before - https://github.com/ACCESS-NRI/ACCESS-ESM1.6/actions/runs/22752303112/job/65989380495?pr=193#step:15:1399

==> [2026-03-06-17:45:21.922157] InstallError: Terminating after first install failure: Cannot replace b'/g/data/vk83/prerelease/apps/spack/1.1/release' with b'/g/data/vk83/prerelease/apps/spack/1.1/restricted/ukmo/release' because the new prefix is longer. To fix this, compile with more padding (config:install_tree:padded_length), or install to a shorter prefix.
==> [2026-03-06-17:45:21.922270] Error: Terminating after first install failure: Cannot replace b'/g/data/vk83/prerelease/apps/spack/1.1/release' with b'/g/data/vk83/prerelease/apps/spack/1.1/restricted/ukmo/release' because the new prefix is longer. To fix this, compile with more padding (config:install_tree:padded_length), or install to a shorter prefix.

manodeep · 2026-03-06T08:20:00Z

There's at least one more failure for the same reason (for gmake) higher up in the log - here

github-actions · 2026-03-06T08:38:24Z

🚀 Attempted to deploy access-esm1p6 Prerelease pr193-8 with commit 5522772

🖥️ `Gadi` Deployment ❌

manodeep · 2026-03-10T04:12:40Z

!redeploy

github-actions · 2026-03-10T04:22:48Z

🚀 Attempted to deploy access-esm1p6 Prerelease pr193-9 with commit 5522772

🖥️ `Gadi` Deployment ❌

manodeep · 2026-03-10T04:47:18Z

Interesting - this failed because of the -xsapphirerapids flag which gets passed to the compiler during the configure step in oasis3-mct, and because the compiling is happening on a cascadelake core (On the login-node), the resulting exe does not run. Here's the relevant text from config.log

icx: warning: overriding '-march=x86-64-v4' option with '-x sapphirerapids' [-Woverriding-option]
configure:2960: $? = 0
configure:2967: ./conftest

Please verify that both the operating system and the processor support Intel(R) AVX512VBMI, AVX512_VPOPCNTDQ, AVX512_BITALG, AVX512_VBMI2 and AVX512_FP16 instructions.

configure:2971: $? = 1
configure:2978: error: in `/scratch/tm70/tm70_ci/tmp/restricted/spack-stage/spack-stage-oasis3-mct-5.2-gqvm7znr6oyjkfjcfpu3wwkkorir4xbi/spack-src/compile_oa3-mct/build/lib/mctdir':
configure:2980: error: cannot run C compiled programs.
If you meant to cross compile, use `--host'.
See `config.log' for more details

Seems to be potentially solvable by a configure argument like --host=sapphirerapids

This section in the autoconf docs is relevant. Adding --host enables cross-compilation and then autoconf does not run any tests that require running the compiled exe

Side-note: Why is it (almost) always oasis3-mct 😅

github-actions · 2026-03-16T12:48:17Z

🚀 Attempted to deploy access-esm1p6 Prerelease pr193-10 with commit 82e41f9

🖥️ `Gadi` Deployment ✔️

Usage Instructions

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

2026.02.001 as a Release (when merged).
pr193-10 as a Prerelease (during this PR).

This Prerelease is accessible on Gadi using:

module use /g/data/vk83/prerelease/modules
module load access-esm1p6/pr193-10

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-esm1p6-pr193-10 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 0b247731bdb7180bfaf1f51d3f9aeaf22a4e2b55
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.

Build with optimisation set in SPR, and with the bug-fix from Martin

0cd6217

manodeep marked this pull request as draft March 4, 2026 11:19

manodeep had a problem deploying to Gadi Prerelease March 4, 2026 11:21 — with GitHub Actions Failure

Use the commit with FO not F0 as the opt level

2abe560

manodeep temporarily deployed to Gadi Prerelease March 4, 2026 11:43 — with GitHub Actions Inactive

Building with the UM7 bug-fix commit hash after rebasing dev-access-e…

81c460c

…sm1p6

manodeep had a problem deploying to Gadi Prerelease March 5, 2026 23:12 — with GitHub Actions Failure

Add O2 to gcom4

6c25bc1

manodeep temporarily deployed to Gadi Prerelease March 6, 2026 03:54 — with GitHub Actions Inactive

Let's go nuts - add O2 and xsapphirerapids to all built pkgs

a4bfaa8

manodeep had a problem deploying to Gadi Prerelease March 6, 2026 06:41 — with GitHub Actions Failure

Fine - removing the arch and opt flags from the lower-level dependencies

5522772

manodeep had a problem deploying to Gadi Prerelease March 6, 2026 08:33 — with GitHub Actions Failure

Compromise to try with cascadelake, which the login node cpus support

82e41f9

manodeep deployed to Gadi Prerelease March 16, 2026 12:18 — with GitHub Actions Active

Conversation

manodeep commented Mar 4, 2026 • edited by github-actions bot Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

github-actions bot commented Mar 4, 2026

Uh oh!

github-actions bot commented Mar 4, 2026

🖥️ Gadi Deployment ❌

Uh oh!

github-actions bot commented Mar 4, 2026

🖥️ Gadi Deployment ❌

Uh oh!

github-actions bot commented Mar 4, 2026

🖥️ Gadi Deployment ✔️

Uh oh!

manodeep commented Mar 4, 2026

Uh oh!

github-actions bot commented Mar 4, 2026

Uh oh!

manodeep commented Mar 5, 2026

Uh oh!

github-actions bot commented Mar 5, 2026

🖥️ Gadi Deployment ❌

Uh oh!

github-actions bot commented Mar 5, 2026

🖥️ Gadi Deployment ❌

Uh oh!

manodeep commented Mar 5, 2026

Uh oh!

manodeep commented Mar 5, 2026

Uh oh!

github-actions bot commented Mar 6, 2026

🖥️ Gadi Deployment ✔️

Uh oh!

manodeep commented Mar 6, 2026

Uh oh!

github-actions bot commented Mar 6, 2026

Uh oh!

github-actions bot commented Mar 6, 2026

🖥️ Gadi Deployment ✔️

Uh oh!

github-actions bot commented Mar 6, 2026

🖥️ Gadi Deployment ❌

Uh oh!

manodeep commented Mar 6, 2026

Uh oh!

manodeep commented Mar 6, 2026

Uh oh!

github-actions bot commented Mar 6, 2026

🖥️ Gadi Deployment ❌

Uh oh!

manodeep commented Mar 10, 2026

Uh oh!

github-actions bot commented Mar 10, 2026

🖥️ Gadi Deployment ❌

Uh oh!

manodeep commented Mar 10, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

github-actions bot commented Mar 16, 2026

🖥️ Gadi Deployment ✔️

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

1 participant

manodeep commented Mar 4, 2026 •

edited by github-actions bot

Loading

🖥️ `Gadi` Deployment ❌

🖥️ `Gadi` Deployment ❌

🖥️ `Gadi` Deployment ✔️

🖥️ `Gadi` Deployment ❌

🖥️ `Gadi` Deployment ❌

🖥️ `Gadi` Deployment ✔️

🖥️ `Gadi` Deployment ✔️

🖥️ `Gadi` Deployment ❌

🖥️ `Gadi` Deployment ❌

🖥️ `Gadi` Deployment ❌

manodeep commented Mar 10, 2026 •

edited

Loading

🖥️ `Gadi` Deployment ✔️