Skip to content

Test for cice5 master branch merge#178

Closed
anton-seaice wants to merge 19 commits intomainfrom
master_merge
Closed

Test for cice5 master branch merge#178
anton-seaice wants to merge 19 commits intomainfrom
master_merge

Conversation

@anton-seaice
Copy link
Collaborator

@anton-seaice anton-seaice commented Jan 5, 2026


🚀 The latest prerelease access-esm1p6/pr178-20 at 0880423 is here: #178 (comment) 🚀

@github-actions
Copy link

github-actions bot commented Jan 5, 2026

🚀 Attempted to deploy access-esm1p6 Prerelease pr178-1 with commit 287ec4e

🖥️ Gadi Deployment ✔️

Usage Instructions

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

  • 2025.12.001 as a Release (when merged).
  • pr178-1 as a Prerelease (during this PR).

This Prerelease is accessible on Gadi using:

module use /g/data/vk83/prerelease/modules
module load access-esm1p6/pr178-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/0.22/spack in the access-esm1p6-pr178-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:

If the above was not what was expected, commit changes to config/versions.json in this PR.

@anton-seaice
Copy link
Collaborator Author

!update-configs

@github-actions
Copy link

github-actions bot commented Jan 5, 2026

🔧 Opening Model Configuration PRs in an unknown configs repository

❌ One or more errors occurred with the workflow

Configurations Requested

No configs were requested.

Pull Requests Opened

No PRs were opened

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

@anton-seaice
Copy link
Collaborator Author

!update-configs

@github-actions
Copy link

github-actions bot commented Jan 5, 2026

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

Configurations Requested

Configurations requested from profile default:

  • dev-preindustrial+concentrations
Pull Requests Opened

The following PRs were opened:

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

@github-actions
Copy link

github-actions bot commented Jan 5, 2026

🚀 Attempted to deploy access-esm1p6 Prerelease pr178-2 with commit 22dbb1d

🖥️ Gadi Deployment ✔️

Usage Instructions

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

  • 2025.12.001 as a Release (when merged).
  • pr178-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/pr178-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/0.22/spack in the access-esm1p6-pr178-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:

If the above was not what was expected, commit changes to config/versions.json in this PR.

@github-actions
Copy link

github-actions bot commented Jan 5, 2026

🚀 Attempted to deploy access-esm1p6 Prerelease pr178-3 with commit e975258

🖥️ Gadi Deployment ❌

@github-actions
Copy link

github-actions bot commented Jan 5, 2026

🚀 Attempted to deploy access-esm1p6 Prerelease pr178-4 with commit 3f73c40

🖥️ Gadi Deployment ❌

@github-actions
Copy link

github-actions bot commented Jan 5, 2026

🚀 Attempted to deploy access-esm1p6 Prerelease pr178-5 with commit 15d3802

🖥️ Gadi Deployment ✔️

Usage Instructions

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

  • 2025.12.001 as a Release (when merged).
  • pr178-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/pr178-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/0.22/spack in the access-esm1p6-pr178-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:

If the above was not what was expected, commit changes to config/versions.json in this PR.

@github-actions
Copy link

github-actions bot commented Jan 6, 2026

🚀 Attempted to deploy access-esm1p6 Prerelease pr178-6 with commit b04c3ca

🖥️ Gadi Deployment ✔️

Usage Instructions

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

  • 2025.12.001 as a Release (when merged).
  • pr178-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/pr178-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/0.22/spack in the access-esm1p6-pr178-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:

If the above was not what was expected, commit changes to config/versions.json in this PR.

@github-actions
Copy link

github-actions bot commented Jan 7, 2026

🚀 Attempted to deploy access-esm1p6 Prerelease pr178-7 with commit 68dc131

🖥️ Gadi Deployment ✔️

Usage Instructions

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

  • 2025.12.001 as a Release (when merged).
  • pr178-7 as a Prerelease (during this PR).

This Prerelease is accessible on Gadi using:

module use /g/data/vk83/prerelease/modules
module load access-esm1p6/pr178-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/0.22/spack in the access-esm1p6-pr178-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:

If the above was not what was expected, commit changes to config/versions.json in this PR.

@github-actions
Copy link

github-actions bot commented Jan 7, 2026

🚀 Attempted to deploy access-esm1p6 Prerelease pr178-8 with commit f458a43

🖥️ Gadi Deployment ✔️

Usage Instructions

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

  • 2025.12.001 as a Release (when merged).
  • pr178-8 as a Prerelease (during this PR).

This Prerelease is accessible on Gadi using:

module use /g/data/vk83/prerelease/modules
module load access-esm1p6/pr178-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/0.22/spack in the access-esm1p6-pr178-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:

If the above was not what was expected, commit changes to config/versions.json in this PR.

@github-actions
Copy link

github-actions bot commented Jan 9, 2026

🚀 Attempted to deploy access-esm1p6 Prerelease pr178-12 with commit 1b964f9

🖥️ Gadi Deployment ✔️

Usage Instructions

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

  • 2025.12.001 as a Release (when merged).
  • pr178-12 as a Prerelease (during this PR).

This Prerelease is accessible on Gadi using:

module use /g/data/vk83/prerelease/modules
module load access-esm1p6/pr178-12

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/0.22/spack in the access-esm1p6-pr178-12 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:

If the above was not what was expected, commit changes to config/versions.json in this PR.

@github-actions
Copy link

github-actions bot commented Jan 9, 2026

🚀 Attempted to deploy access-esm1p6 Prerelease pr178-13 with commit deba305

🖥️ Gadi Deployment ❌

@anton-seaice
Copy link
Collaborator Author

!redeploy

@github-actions
Copy link

github-actions bot commented Jan 9, 2026

🚀 Attempted to deploy access-esm1p6 Prerelease pr178-14 with commit deba305

🖥️ Gadi Deployment ✔️

Usage Instructions

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

  • 2025.12.001 as a Release (when merged).
  • pr178-14 as a Prerelease (during this PR).

This Prerelease is accessible on Gadi using:

module use /g/data/vk83/prerelease/modules
module load access-esm1p6/pr178-14

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/0.22/spack in the access-esm1p6-pr178-14 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:

If the above was not what was expected, commit changes to config/versions.json in this PR.

@anton-seaice
Copy link
Collaborator Author

!update-configs

@github-actions
Copy link

github-actions bot commented Jan 9, 2026

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

Configurations Requested

Configurations requested from profile default:

  • dev-preindustrial+concentrations
Pull Requests Opened

The following PRs were opened:

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

@github-actions
Copy link

🚀 Attempted to deploy access-esm1p6 Prerelease pr178-15 with commit 5bcd1fc

🖥️ Gadi Deployment ❌

@anton-seaice
Copy link
Collaborator Author

!redeploy

@github-actions
Copy link

🚀 Attempted to deploy access-esm1p6 Prerelease pr178-16 with commit 5bcd1fc

🖥️ Gadi Deployment ✔️

Usage Instructions

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

  • 2025.12.001 as a Release (when merged).
  • pr178-16 as a Prerelease (during this PR).

This Prerelease is accessible on Gadi using:

module use /g/data/vk83/prerelease/modules
module load access-esm1p6/pr178-16

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/0.22/spack in the access-esm1p6-pr178-16 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:

If the above was not what was expected, commit changes to config/versions.json in this PR.

@github-actions
Copy link

🚀 Attempted to deploy access-esm1p6 Prerelease pr178-17 with commit 04317ce

🖥️ Gadi Deployment ✔️

Usage Instructions

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

  • 2025.12.001 as a Release (when merged).
  • pr178-17 as a Prerelease (during this PR).

This Prerelease is accessible on Gadi using:

module use /g/data/vk83/prerelease/modules
module load access-esm1p6/pr178-17

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/0.22/spack in the access-esm1p6-pr178-17 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:

If the above was not what was expected, commit changes to config/versions.json in this PR.

@github-actions
Copy link

🚀 Attempted to deploy access-esm1p6 Prerelease pr178-18 with commit ede9d21

🖥️ Gadi Deployment ✔️

Usage Instructions

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

  • 2025.12.001 as a Release (when merged).
  • pr178-18 as a Prerelease (during this PR).

This Prerelease is accessible on Gadi using:

module use /g/data/vk83/prerelease/modules
module load access-esm1p6/pr178-18

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/0.22/spack in the access-esm1p6-pr178-18 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:

If the above was not what was expected, commit changes to config/versions.json in this PR.

@github-actions
Copy link

🚀 Attempted to deploy access-esm1p6 Prerelease pr178-19 with commit 8ec4870

🖥️ Gadi Deployment ✔️

Usage Instructions

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

  • 2025.12.001 as a Release (when merged).
  • pr178-19 as a Prerelease (during this PR).

This Prerelease is accessible on Gadi using:

module use /g/data/vk83/prerelease/modules
module load access-esm1p6/pr178-19

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/0.22/spack in the access-esm1p6-pr178-19 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:

If the above was not what was expected, commit changes to config/versions.json in this PR.

@github-actions
Copy link

🚀 Attempted to deploy access-esm1p6 Prerelease pr178-20 with commit 0880423

🖥️ Gadi Deployment ✔️

Usage Instructions

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

  • 2025.12.001 as a Release (when merged).
  • pr178-20 as a Prerelease (during this PR).

This Prerelease is accessible on Gadi using:

module use /g/data/vk83/prerelease/modules
module load access-esm1p6/pr178-20

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/0.22/spack in the access-esm1p6-pr178-20 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:

If the above was not what was expected, commit changes to config/versions.json in this PR.

@anton-seaice
Copy link
Collaborator Author

Finished with this = ACCESS-NRI/cice5#68 was m,erged

@anton-seaice anton-seaice deleted the master_merge branch January 29, 2026 03:59
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.

1 participant