Skip to content

Build with the head of 47-perf-rho-remap-diags branch of MOM6#236

Draft
manodeep wants to merge 6 commits into
mainfrom
perf-mom6-rho-remap-diags
Draft

Build with the head of 47-perf-rho-remap-diags branch of MOM6#236
manodeep wants to merge 6 commits into
mainfrom
perf-mom6-rho-remap-diags

Conversation

@manodeep

@manodeep manodeep commented Jun 3, 2026

Copy link
Copy Markdown
Collaborator

Draft - do not merge.


🚀 The latest prerelease access-om3/pr236-8 at ba7d1f5 is here: #236 (comment) 🚀

@manodeep manodeep requested a review from a team as a code owner June 3, 2026 04:52
@manodeep manodeep marked this pull request as draft June 3, 2026 04:52
@github-actions

github-actions Bot commented Jun 3, 2026

Copy link
Copy Markdown

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

github-actions Bot commented Jun 3, 2026

Copy link
Copy Markdown

🚀 Attempted to deploy access-om3 Prerelease pr236-1 with commit 289e371

🖥️ Gadi Deployment ❌

@github-actions

github-actions Bot commented Jun 3, 2026

Copy link
Copy Markdown

🚀 Attempted to deploy access-om3 Prerelease pr236-1 with commit 289e371

🖥️ Gadi Deployment ❌

@CodeGat

CodeGat commented Jun 3, 2026

Copy link
Copy Markdown
Member

!redeploy

@github-actions

github-actions Bot commented Jun 3, 2026

Copy link
Copy Markdown

🚀 Attempted to deploy access-om3 Prerelease pr236-2 with commit 289e371

🖥️ Gadi Deployment ✔️

Usage Instructions

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

  • 2026.05.001 as a Release (when merged).
  • pr236-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/pr236-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-pr236-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.05.004
  • 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.

@manodeep

manodeep commented Jun 3, 2026

Copy link
Copy Markdown
Collaborator Author

!update-configs

@github-actions

github-actions Bot commented Jun 3, 2026

Copy link
Copy Markdown

🔧 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:

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

@manodeep manodeep temporarily deployed to Gadi Prerelease June 4, 2026 05:53 — with GitHub Actions Inactive
@github-actions

github-actions Bot commented Jun 4, 2026

Copy link
Copy Markdown

🚀 Attempted to deploy access-om3 Prerelease pr236-3 with commit 0230cb4

🖥️ Gadi Deployment ✔️

Usage Instructions

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

  • 2026.05.001 as a Release (when merged).
  • pr236-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/pr236-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-pr236-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.05.004
  • 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

github-actions Bot commented Jun 4, 2026

Copy link
Copy Markdown

🚀 Attempted to deploy access-om3 Prerelease pr236-4 with commit e28d60a

🖥️ Gadi Deployment ❌

@manodeep

manodeep commented Jun 4, 2026

Copy link
Copy Markdown
Collaborator Author

!redeploy

@github-actions

github-actions Bot commented Jun 4, 2026

Copy link
Copy Markdown

🚀 Attempted to deploy access-om3 Prerelease pr236-5 with commit e28d60a

🖥️ Gadi Deployment ✔️

Usage Instructions

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

  • 2026.05.001 as a Release (when merged).
  • pr236-5 as a Prerelease (during this PR).

This Prerelease is accessible on Gadi using:

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

@manodeep

manodeep commented Jun 4, 2026

Copy link
Copy Markdown
Collaborator Author

!update-configs

@github-actions

github-actions Bot commented Jun 4, 2026

Copy link
Copy Markdown

🔧 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:

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

@manodeep

Copy link
Copy Markdown
Collaborator Author

!redeploy

@github-actions

Copy link
Copy Markdown

🚀 Attempted to deploy access-om3 Prerelease pr236-6 with commit 6f524fc

🖥️ Gadi Deployment ✔️

Usage Instructions

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

  • 2026.05.001 as a Release (when merged).
  • pr236-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/pr236-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-pr236-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 2026.05.004
  • 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.

@manodeep

Copy link
Copy Markdown
Collaborator Author

!redeploy

@github-actions

Copy link
Copy Markdown

🚀 Attempted to deploy access-om3 Prerelease pr236-6 with commit 6f524fc

🖥️ Gadi Deployment ✔️

Usage Instructions

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

  • 2026.05.001 as a Release (when merged).
  • pr236-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/pr236-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-pr236-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 2026.05.004
  • 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

Copy link
Copy Markdown

🚀 Attempted to deploy access-om3 Prerelease pr236-7 with commit 317bb61

🖥️ Gadi Deployment ✔️

Usage Instructions

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

  • 2026.05.001 as a Release (when merged).
  • pr236-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/pr236-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-pr236-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 2026.05.004
  • 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.

@manodeep

Copy link
Copy Markdown
Collaborator Author

!redeploy

@github-actions

Copy link
Copy Markdown

🚀 Attempted to deploy access-om3 Prerelease pr236-8 with commit ba7d1f5

🖥️ Gadi Deployment ✔️

Usage Instructions

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

  • 2026.05.001 as a Release (when merged).
  • pr236-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/pr236-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-pr236-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 2026.05.004
  • 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.

@manodeep

Copy link
Copy Markdown
Collaborator Author

Closed all the auto-PRs to the config repo to check whether invoking update-configs again picks up the latest configs

@manodeep

Copy link
Copy Markdown
Collaborator Author

!update-configs

@github-actions

Copy link
Copy Markdown

🔧 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:

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants