Upgrade openmpi to 5.0.8 by manodeep · Pull Request #264 · ACCESS-NRI/ACCESS-OM3

manodeep · 2026-09-01T09:55:14Z

Previously this had segfaulted but I can't find the original crash directory. Testing again

🚀 The latest prerelease access-om3/pr264-11 at 57f767b is here: #264 (comment) 🚀

github-actions · 2026-09-01T09:55:52Z

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-09-01T09:56:13Z

🚀 Attempted to deploy access-om3 Prerelease pr264-1 with commit cd824a4

🖥️ `Gadi` Deployment ❌

github-actions · 2026-09-01T11:09:14Z

🚀 Attempted to deploy access-om3 Prerelease pr264-1 with commit cd824a4

🖥️ `Gadi` Deployment ✔️

Usage Instructions

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

2026.05.003 as a Release (when merged).
pr264-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/pr264-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-pr264-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.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.

manodeep · 2026-09-01T11:14:42Z

!update-configs

github-actions · 2026-09-01T11:15:48Z

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

❌ One or more errors occurred with the workflow

Configurations Requested

Configurations requested from profile default:

dev-MCW_100km_jra_iaf
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:

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

manodeep · 2026-09-01T11:21:14Z

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

❌ One or more errors occurred with the workflow
Configurations Requested

Configurations requested from profile default:
* `dev-MCW_100km_jra_iaf`

* `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/pr264-1 access-om3-configs#1637](https://github.com/ACCESS-NRI/access-om3-configs/pull/1637)

* [Auto update dev-MC_100km_jra_ryf+wombatlite to use access-om3/pr264-1 access-om3-configs#1638](https://github.com/ACCESS-NRI/access-om3-configs/pull/1638)

* [Auto update dev-MC_25km_jra_ryf to use access-om3/pr264-1 access-om3-configs#1636](https://github.com/ACCESS-NRI/access-om3-configs/pull/1636)
More details can be found in the workflow run: https://github.com/ACCESS-NRI/ACCESS-OM3/actions/runs/33501482275

Apparently, this is meant to update the dev-MCW_100km_jra_iaf branch, but the actions shows the following error:

error: pathspec 'dev-MCW_100km_jra_iaf' did not match any file(s) known to git

@ezhilsabareesh8 ☝🏾

ezhilsabareesh8 · 2026-09-03T11:15:03Z

Apparently, this is meant to update the dev-MCW_100km_jra_iaf branch, but the actions shows the following error:
error: pathspec 'dev-MCW_100km_jra_iaf' did not match any file(s) known to git

@manodeep this branch has been renamed to dev-MCW_100km_era_iaf

manodeep · 2026-09-03T12:13:45Z

Apparently, this is meant to update the dev-MCW_100km_jra_iaf branch, but the actions shows the following error:
error: pathspec 'dev-MCW_100km_jra_iaf' did not match any file(s) known to git
@manodeep this branch has been renamed to dev-MCW_100km_era_iaf

@ezhilsabareesh8 Might mean that a corresponding manifest needs to also be renamed; otherwise the !update-configs command is looking for the original branch.

… patch

manodeep · 2026-09-04T01:41:53Z

Apparently, this is meant to update the dev-MCW_100km_jra_iaf branch, but the actions shows the following error:
error: pathspec 'dev-MCW_100km_jra_iaf' did not match any file(s) known to git
@manodeep this branch has been renamed to dev-MCW_100km_era_iaf
@ezhilsabareesh8 Might mean that a corresponding manifest needs to also be renamed; otherwise the !update-configs command is looking for the original branch.

@ezhilsabareesh8 I couldn't find out where the name update needed to be - but it's on this line

github-actions · 2026-09-04T02:28:11Z

🚀 Attempted to deploy access-om3 Prerelease pr264-2 with commit db8b3c8

🖥️ `Gadi` Deployment ✔️

Usage Instructions

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

2026.05.003 as a Release (when merged).
pr264-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/pr264-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-pr264-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 fc25b02d11312faa6037fd3984048d06946c2aef
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.

manodeep · 2026-09-04T02:38:27Z

Confirming that the stack VLA -> heap array patch was applied

manodeep · 2026-09-04T02:54:43Z

Ran with the latest deployment but there was an error for invalid free immediately on startup, and no further output (in either of the out or err) for the next 7-8 mins. So I qdel'ed the job - need to fix the patch

…ck arrays in write paths too

manodeep · 2026-09-04T03:33:05Z

Claude has "patched" the patch. The previous patch only covered the pio reads; the pio writes still had the same pattern of stack arrays and needed to be converted into heap arrays

github-actions · 2026-09-04T04:21:58Z

🚀 Attempted to deploy access-om3 Prerelease pr264-3 with commit 534cba0

🖥️ `Gadi` Deployment ✔️

Usage Instructions

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

2026.05.003 as a Release (when merged).
pr264-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/pr264-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-pr264-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 9192b6f0ab9001ba57e093388fe6ac1812d03501
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.

harshula · 2026-09-04T10:11:22Z

Hi @manodeep , If you want to test parallelio 2.6.9 or 2.6.10, I've cherry-picked those commits into:

  builtin:
    git: https://github.com/ACCESS-NRI/upstream-spack-packages.git
    branch: access/v1.1-next
    destination: $env/package-repos/spack-packages

You can add the above snippet in the repos: section of the spack.yaml. Whichever repository comes first has higher precedence.

manodeep · 2026-09-04T10:31:09Z

Thanks @harshula! There's some black magic y'all can do with spack recipes 😄

That read/write error is potentially fixed but now I have a different error (invalid free and no stack trace, and a hanging + resource-consuming MPI job 😞)

manodeep · 2026-09-05T05:23:26Z

Running with env vars for checking malloc, I get a crash with the released version of access-om3 for 25k-IAF config - so the bug (bugs?) affect both configs, and pre-existing.

env:
  MALLOC_CHECK_: 3
  MALLOC_PERTURB_: 42
  MALLOC_ARENA_MAX: 1

github-actions · 2026-09-05T11:57:18Z

🚀 Attempted to deploy access-om3 Prerelease pr264-6 with commit 45dcff7

🖥️ `Gadi` Deployment ✔️

Usage Instructions

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

2026.05.003 as a Release (when merged).
pr264-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/pr264-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-pr264-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
ACCESS-NRI/upstream-spack-packages version access/v1.1
access-nri/access-spack-packages version cef99e19323cdc0e1e121f6d87b89cc2f9000cae
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.

manodeep · 2026-09-05T12:13:01Z

!update-configs

github-actions · 2026-09-05T12:14:34Z

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

Configurations Requested

Configurations requested from profile default:

dev-MCW_100km_era_iaf
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:

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

manodeep · 2026-09-05T12:47:34Z

All the configs pass the repro tests except for test_repro_payu_setup - which is expected since I am changing the exe

manodeep · 2026-09-06T02:53:03Z

Big boost (~18% faster) in runtime performance for a 1-yr 25k RYF run - 2h45mins vs 3h22mins for the released model with openmpi/4.1.7 and the PIO bug; 14.9 kSU vs 18.3 kSU 🚀. Bitwise identical results.

[~/perf-om3/25km/test-ompi-508 @gadi-login-08]$ ~/perf-om3/om3_summary.sh 25km_jra_ryf_Sep2_1yr_cloned_from_patched_ompi508 25km_jra_ryf_Sep2_1yr_ompi_508_pio_patched_write_esmf_zoltan_patched
Using command-line directory pattern: '25km_jra_ryf_Sep2_1yr_cloned_from_patched_ompi508 25km_jra_ryf_Sep2_1yr_ompi_508_pio_patched_write_esmf_zoltan_patched'
Progress : [########################################] 100%

Printing runtime results (all times are in mins, sorted by 'Simulated Years per wallclock-day'):

yrs/Wday	WTime (max ocn/wtime)	SUs	CPUs	yrs/core/Wday	Directory
8.8	164.5 (73.9%)	14825	2704	3.24e-03	25km_jra_ryf_Sep2_1yr_ompi_508_pio_patched_write_esmf_zoltan_patched
7.1	202.3 (74.5%)	18231	2704	2.63e-03	25km_jra_ryf_Sep2_1yr_cloned_from_patched_ompi508

Bitwise repro passes

[~/perf-om3/25km/test-ompi-508 @gadi-login-08]$ compare-exp-tests --dirs "25km_jra_ryf_Sep2_1yr_cloned_from_patched_ompi508 25km_jra_ryf_Sep2_1yr_ompi_508_pio_patched_write_esmf_zoltan_patched"
Test session starts (platform: linux, Python 3.12.1, pytest 9.1.1, pytest-sugar 1.1.1)
rootdir: /home/593/ms2335/codes/utils/model-config-tests/src/model_config_tests/compare_exp_tests
configfile: ../../../pyproject.toml
plugins: cov-7.0.0, anyio-4.11.0, sugar-1.1.1, hypothesis-6.92.6
collected 1 item                                                                                                                                                                                      

 test_repro.py ✓                                                                                                                                                                        100% ██████████

Results (1.54s):
       1 passed

Caveats: Single runs (not min. of repeated runs), and the two experiments were done at different times - the patched expt was yesterday, and the released one was this morning

dougiesquire · 2026-09-06T22:30:07Z

Nice work @manodeep! Will you open issues/PRs for the parallelio and esmf fixes?

manodeep · 2026-09-07T10:41:04Z

That's the goal - assuming we all agree that the PIO and ESMF patches are correct (or at least in the ballpark). Are you able to take a look at the two patches?

I also have a stockpile of PRs that I need to work through (the CICE runtime changes, this one with the OpenMPI upgrade, and the repro-preserving non-blocking update for MOM6, plus the yet-to-be-pushed-to-GH ACCESS-FMS/ESM1.6 collective netcdf-io upgrade)

… code changes (relevant for the upcoming 8k run)

github-actions · 2026-09-07T11:03:09Z

🚀 Attempted to deploy access-om3 Prerelease pr264-7 with commit f4c1ba2

🖥️ `Gadi` Deployment ✔️

Usage Instructions

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

2026.05.003 as a Release (when merged).
pr264-7 as a Prerelease (during this PR).

This Prerelease is accessible on Gadi using:

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

manodeep · 2026-09-07T23:39:03Z

More perf tests

IAF (30-day runs only)

yrs/Wday	WTime (max ocn/wtime)	SUs	CPUs	yrs/core/Wday	Directory
8.4	14.1 (63.1%)	1271	2704	3.10e-03	25km_jra_iaf_Sep6_30days_pr264-7_with_mom6_perf-rho-branch_deflate_1
8.1	14.6 (62.0%)	1320	2704	2.99e-03	25km_jra_iaf_Sep6_30days_pr264-7_with_mom6_perf-rho-branch
7.9	15.0 (68.0%)	1353	2704	2.91e-03	25km_jra_iaf_Sep6_30days_pr264-5_patched_pio_patched_Zoltan
7.8	15.3 (58.0%)	1375	2704	2.87e-03	25km_jra_iaf_Sep6_30days_pr264-7_with_mom6_perf-rho-branch_deflate_1_flush_nc_false
7.4	15.9 (56.0%)	1433	2704	2.75e-03	25km_jra_iaf_Sep6_30days_pr264-7_with_mom6_perf-rho-branch_flush_nc_false
6.1	19.3 (66.0%)	1736	2704	2.27e-03	25km_jra_iaf_Sep6_30days_cloned_from_patched_ompi508 (released)

RYF (Mix of 30-days and 1-yr)

yrs/Wday	WTime (max ocn/wtime)	SUs	CPUs	yrs/core/Wday	Directory
8.8	164.5 (73.9%)	14825	2704	3.24e-03	25km_jra_ryf_Sep2_1yr_ompi_508_pio_patched_write_esmf_zoltan_patched
8.7	165.8 (73.5%)	14943	2704	3.21e-03	25km_jra_ryf_Sep2_1yr_ompi_508_pio_patched_write_esmf_zoltan_patched_deflate_1
8.2	175.7 (61.7%)	15840	2704	3.03e-03	25km_jra_ryf_Sep2_1yr_ompi_508_pr264-7_patched_pio_zoltan_mom6_perf-rho-remap
7.1	202.3 (74.5%)	18231	2704	2.63e-03	25km_jra_ryf_Sep2_1yr_cloned_from_patched_ompi508 (released)
6.3	18.7 (67.2%)	1689	2704	2.33e-03	25km_jra_ryf_Sep2_30days_deflate_1_shuffle_false
6.3	18.8 (67.5%)	1696	2704	2.33e-03	25km_jra_ryf_Sep2_30days_deflate_1
6.2	19.1 (67.8%)	1718	2704	2.30e-03	25km_jra_ryf_Sep2_30days_deflate_0
6.0	19.6 (64.1%)	1771	2704	2.23e-03	25km_jra_ryf_Sep2_30days (released)

manodeep · 2026-09-08T06:15:20Z

This PR is now being used for deploying the 8k run this week. Will have to redo once we decide to merge in the OpenMPI changes (or switch out to a different branch with only the OpenMPI v5 commits)

github-actions · 2026-09-08T06:22:25Z

🚀 Attempted to deploy access-om3 Prerelease pr264-8 with commit fcddadd

🖥️ `Gadi` Deployment ✔️

Usage Instructions

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

2026.05.003 as a Release (when merged).
pr264-8 as a Prerelease (during this PR).

This Prerelease is accessible on Gadi using:

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

…e + openmpi v5 changes)

github-actions · 2026-09-08T07:23:03Z

🚀 Attempted to deploy access-om3 Prerelease pr264-9 with commit 5a17f63

🖥️ `Gadi` Deployment ✔️

Usage Instructions

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

2026.05.003 as a Release (when merged).
pr264-9 as a Prerelease (during this PR).

This Prerelease is accessible on Gadi using:

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

manodeep · 2026-09-09T13:11:43Z

Nice work @manodeep! Will you open issues/PRs for the parallelio and esmf fixes?

PIO issue and ESMF issue

github-actions · 2026-09-09T23:17:00Z

🚀 Attempted to deploy access-om3 Prerelease pr264-10 with commit 73c3366

🖥️ `Gadi` Deployment ✔️

Usage Instructions

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

2026.05.003 as a Release (when merged).
pr264-10 as a Prerelease (during this PR).

This Prerelease is accessible on Gadi using:

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

github-actions · 2026-09-10T12:45:10Z

🚀 Attempted to deploy access-om3 Prerelease pr264-11 with commit 57f767b

🖥️ `Gadi` Deployment ✔️

Usage Instructions

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

2026.05.003 as a Release (when merged).
pr264-11 as a Prerelease (during this PR).

This Prerelease is accessible on Gadi using:

module use /g/data/vk83/prerelease/modules
module load access-om3/pr264-11

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-pr264-11 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 5b9cc63f2324b14133f88b2e993ee173ba08955e
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.

Upgrade openmpi to 5.0.8

cd824a4

manodeep requested a review from a team as a code owner September 1, 2026 09:55

manodeep marked this pull request as draft September 1, 2026 09:55

manodeep removed the request for review from a team September 1, 2026 09:55

manodeep temporarily deployed to Gadi Prerelease September 1, 2026 09:57 — with GitHub Actions Inactive

Hopefully this is how to pickup the pio SPR update with the stack VLA…

db8b3c8

… patch

manodeep temporarily deployed to Gadi Prerelease September 4, 2026 01:42 — with GitHub Actions Inactive

aidanheerdegen mentioned this pull request Sep 4, 2026

Set reduced wall time in repro tests to avoid excessive resource use ACCESS-NRI/model-config-tests#248

Closed

Enable logging for pio, and then build with the patch that covers sta…

534cba0

…ck arrays in write paths too

manodeep temporarily deployed to Gadi Prerelease September 4, 2026 03:34 — with GitHub Actions Inactive

Fix the MCW branch name

45dcff7

manodeep temporarily deployed to Gadi Prerelease September 5, 2026 11:54 — with GitHub Actions Inactive

access-bot mentioned this pull request Sep 5, 2026

Auto update dev-MCW_100km_era_iaf to use access-om3/pr264-6 ACCESS-NRI/access-om3-configs#1641

Draft

Because I have no chill and need to know the perf. boost from my MOM6…

f4c1ba2

… code changes (relevant for the upcoming 8k run)

manodeep temporarily deployed to Gadi Prerelease September 7, 2026 10:52 — with GitHub Actions Inactive

Replace perf-rho-remap branch with the MOM6 nonblocking-update patch

fcddadd

manodeep temporarily deployed to Gadi Prerelease September 8, 2026 05:55 — with GitHub Actions Inactive

Added the profile use flag (on top of the nonblocking update MOM6 cod…

5a17f63

…e + openmpi v5 changes)

manodeep temporarily deployed to Gadi Prerelease September 8, 2026 06:25 — with GitHub Actions Inactive

Redploy with the profiling data from a 10-day run using the C-grid

73c3366

manodeep temporarily deployed to Gadi Prerelease September 9, 2026 22:14 — with GitHub Actions Inactive

harshula mentioned this pull request Sep 10, 2026

gcom: support %oneapi ACCESS-NRI/access-spack-packages#496

Open

Try with this Claude-fix for another potential PIO bug

57f767b

manodeep deployed to Gadi Prerelease September 10, 2026 11:26 — with GitHub Actions Active

minghangli-uni mentioned this pull request Sep 11, 2026

Updating Angus' 8km ryf configuration to use the latest dev-MC_25km_jra_ryf ACCESS-NRI/access-om3-configs#1432

Draft

Uh oh!

Conversation

manodeep commented Sep 1, 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 Sep 1, 2026

Uh oh!

github-actions Bot commented Sep 1, 2026

🖥️ Gadi Deployment ❌

Uh oh!

github-actions Bot commented Sep 1, 2026

🖥️ Gadi Deployment ✔️

Uh oh!

manodeep commented Sep 1, 2026

Uh oh!

github-actions Bot commented Sep 1, 2026

Uh oh!

manodeep commented Sep 1, 2026

Uh oh!

ezhilsabareesh8 commented Sep 3, 2026

Uh oh!

manodeep commented Sep 3, 2026

Uh oh!

manodeep commented Sep 4, 2026

Uh oh!

github-actions Bot commented Sep 4, 2026

🖥️ Gadi Deployment ✔️

Uh oh!

manodeep commented Sep 4, 2026

Uh oh!

manodeep commented Sep 4, 2026

Uh oh!

manodeep commented Sep 4, 2026

Uh oh!

github-actions Bot commented Sep 4, 2026

🖥️ Gadi Deployment ✔️

Uh oh!

harshula commented Sep 4, 2026

Uh oh!

manodeep commented Sep 4, 2026

Uh oh!

manodeep commented Sep 5, 2026

Uh oh!

github-actions Bot commented Sep 5, 2026

🖥️ Gadi Deployment ✔️

Uh oh!

manodeep commented Sep 5, 2026

Uh oh!

github-actions Bot commented Sep 5, 2026

Uh oh!

manodeep commented Sep 5, 2026

Uh oh!

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

Uh oh!

Uh oh!

dougiesquire commented Sep 6, 2026

Uh oh!

manodeep commented Sep 7, 2026

Uh oh!

github-actions Bot commented Sep 7, 2026

🖥️ Gadi Deployment ✔️

Uh oh!

manodeep commented Sep 7, 2026

IAF (30-day runs only)

RYF (Mix of 30-days and 1-yr)

Uh oh!

manodeep commented Sep 8, 2026

Uh oh!

github-actions Bot commented Sep 8, 2026

🖥️ Gadi Deployment ✔️

Uh oh!

github-actions Bot commented Sep 8, 2026

🖥️ Gadi Deployment ✔️

Uh oh!

manodeep commented Sep 9, 2026

Uh oh!

github-actions Bot commented Sep 9, 2026

🖥️ Gadi Deployment ✔️

Uh oh!

github-actions Bot commented Sep 10, 2026

manodeep commented Sep 1, 2026 •

edited by github-actions Bot

Loading

🖥️ `Gadi` Deployment ❌

🖥️ `Gadi` Deployment ✔️

🖥️ `Gadi` Deployment ✔️

🖥️ `Gadi` Deployment ✔️

🖥️ `Gadi` Deployment ✔️

manodeep commented Sep 6, 2026 •

edited

Loading

🖥️ `Gadi` Deployment ✔️

🖥️ `Gadi` Deployment ✔️

🖥️ `Gadi` Deployment ✔️

🖥️ `Gadi` Deployment ✔️

🖥️ `Gadi` Deployment ✔️