Skip to content

Test for cice5 esm1.6-> master branch merge#131

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

Test for cice5 esm1.6-> master branch merge#131
anton-seaice wants to merge 16 commits intomainfrom
master_merge

Conversation

@anton-seaice
Copy link
Collaborator

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


🚀 The latest prerelease access-om2/pr131-20 at 157f411 is here: #131 (comment) 🚀

@anton-seaice anton-seaice changed the title Test for esm1.6-> master branch merge Test for cice5 esm1.6-> master branch merge Jan 5, 2026
@github-actions
Copy link
Contributor

github-actions bot commented Jan 5, 2026

🚀 Attempted to deploy access-om2 Prerelease pr131-1 with commit 3379d4d

🖥️ Gadi Deployment ❌

@anton-seaice
Copy link
Collaborator Author

!redeploy

@github-actions
Copy link
Contributor

github-actions bot commented Jan 5, 2026

🚀 Attempted to deploy access-om2 Prerelease pr131-2 with commit 3379d4d

🖥️ Gadi Deployment ✔️

Usage Instructions

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

  • 2025.12.000 as a Release (when merged).
  • pr131-2 as a Prerelease (during this PR).

This Prerelease is accessible on Gadi using:

module use /g/data/vk83/prerelease/modules
module load access-om2/pr131-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-om2-pr131-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
Contributor

github-actions bot commented Jan 5, 2026

🚀 Attempted to deploy access-om2 Prerelease pr131-3 with commit 1cdfa75

🖥️ Gadi Deployment ✔️

Usage Instructions

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

  • 2025.12.000 as a Release (when merged).
  • pr131-3 as a Prerelease (during this PR).

This Prerelease is accessible on Gadi using:

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

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

@github-actions
Copy link
Contributor

github-actions bot commented Jan 6, 2026

🚀 Attempted to deploy access-om2 Prerelease pr131-4 with commit 2f7c4c1

🖥️ Gadi Deployment ✔️

Usage Instructions

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

  • 2025.12.000 as a Release (when merged).
  • pr131-4 as a Prerelease (during this PR).

This Prerelease is accessible on Gadi using:

module use /g/data/vk83/prerelease/modules
module load access-om2/pr131-4

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-om2-pr131-4 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
Contributor

github-actions bot commented Jan 7, 2026

🚀 Attempted to deploy access-om2 Prerelease pr131-5 with commit a32662a

🖥️ Gadi Deployment ✔️

Usage Instructions

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

  • 2025.12.000 as a Release (when merged).
  • pr131-5 as a Prerelease (during this PR).

This Prerelease is accessible on Gadi using:

module use /g/data/vk83/prerelease/modules
module load access-om2/pr131-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-om2-pr131-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
Contributor

github-actions bot commented Jan 7, 2026

🚀 Attempted to deploy access-om2 Prerelease pr131-6 with commit 32a293a

🖥️ Gadi Deployment ✔️

Usage Instructions

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

  • 2025.12.000 as a Release (when merged).
  • pr131-6 as a Prerelease (during this PR).

This Prerelease is accessible on Gadi using:

module use /g/data/vk83/prerelease/modules
module load access-om2/pr131-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-om2-pr131-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
Contributor

github-actions bot commented Jan 8, 2026

🚀 Attempted to deploy access-om2 Prerelease pr131-7 with commit ab7e9dd

🖥️ Gadi Deployment ✔️

Usage Instructions

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

  • 2025.12.000 as a Release (when merged).
  • pr131-7 as a Prerelease (during this PR).

This Prerelease is accessible on Gadi using:

module use /g/data/vk83/prerelease/modules
module load access-om2/pr131-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-om2-pr131-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
Contributor

github-actions bot commented Jan 9, 2026

🚀 Attempted to deploy access-om2 Prerelease pr131-8 with commit 47f7256

🖥️ Gadi Deployment ✔️

Usage Instructions

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

  • 2025.12.000 as a Release (when merged).
  • pr131-8 as a Prerelease (during this PR).

This Prerelease is accessible on Gadi using:

module use /g/data/vk83/prerelease/modules
module load access-om2/pr131-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-om2-pr131-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
Contributor

github-actions bot commented Jan 9, 2026

🚀 Attempted to deploy access-om2 Prerelease pr131-9 with commit 663fb44

🖥️ Gadi Deployment ✔️

Usage Instructions

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

  • 2025.12.000 as a Release (when merged).
  • pr131-9 as a Prerelease (during this PR).

This Prerelease is accessible on Gadi using:

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

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

@github-actions
Copy link
Contributor

🚀 Attempted to deploy access-om2 Prerelease pr131-10 with commit 9f0eddc

🖥️ Gadi Deployment ✔️

Usage Instructions

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

  • 2025.12.000 as a Release (when merged).
  • pr131-10 as a Prerelease (during this PR).

This Prerelease is accessible on Gadi using:

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

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

@github-actions
Copy link
Contributor

🚀 Attempted to deploy access-om2 Prerelease pr131-11 with commit 4d56bed

🖥️ Gadi Deployment ❌

@anton-seaice
Copy link
Collaborator Author

!redeploy

@github-actions
Copy link
Contributor

🚀 Attempted to deploy access-om2 Prerelease pr131-12 with commit 4d56bed

🖥️ Gadi Deployment ✔️

Usage Instructions

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

  • 2025.12.000 as a Release (when merged).
  • pr131-12 as a Prerelease (during this PR).

This Prerelease is accessible on Gadi using:

module use /g/data/vk83/prerelease/modules
module load access-om2/pr131-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-om2-pr131-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
Contributor

🚀 Attempted to deploy access-om2 Prerelease pr131-13 with commit 5e0b3d6

🖥️ Gadi Deployment ✔️

Usage Instructions

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

  • 2025.12.000 as a Release (when merged).
  • pr131-13 as a Prerelease (during this PR).

This Prerelease is accessible on Gadi using:

module use /g/data/vk83/prerelease/modules
module load access-om2/pr131-13

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-om2-pr131-13 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
Contributor

🚀 Attempted to deploy access-om2 Prerelease pr131-14 with commit 604d8e0

🖥️ Gadi Deployment ✔️

Usage Instructions

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

  • 2025.12.000 as a Release (when merged).
  • pr131-14 as a Prerelease (during this PR).

This Prerelease is accessible on Gadi using:

module use /g/data/vk83/prerelease/modules
module load access-om2/pr131-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-om2-pr131-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.

@github-actions
Copy link
Contributor

🚀 Attempted to deploy access-om2 Prerelease pr131-15 with commit 42467d9

🖥️ Gadi Deployment ✔️

Usage Instructions

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

  • 2025.12.000 as a Release (when merged).
  • pr131-15 as a Prerelease (during this PR).

This Prerelease is accessible on Gadi using:

module use /g/data/vk83/prerelease/modules
module load access-om2/pr131-15

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-om2-pr131-15 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
Contributor

🚀 Attempted to deploy access-om2 Prerelease pr131-16 with commit fd0c0e6

🖥️ Gadi Deployment ✔️

Usage Instructions

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

  • 2025.12.000 as a Release (when merged).
  • pr131-16 as a Prerelease (during this PR).

This Prerelease is accessible on Gadi using:

module use /g/data/vk83/prerelease/modules
module load access-om2/pr131-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-om2-pr131-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.

@anton-seaice
Copy link
Collaborator Author

!test repro

@github-actions
Copy link
Contributor

🚀 Attempted to deploy access-om2 Prerelease pr131-17 with commit 9666e4a

🖥️ Gadi Deployment ❌

@anton-seaice
Copy link
Collaborator Author

!redeploy

@github-actions
Copy link
Contributor

🚀 Attempted to deploy access-om2 Prerelease pr131-18 with commit 9666e4a

🖥️ Gadi Deployment ✔️

Usage Instructions

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

  • 2025.12.000 as a Release (when merged).
  • pr131-18 as a Prerelease (during this PR).

This Prerelease is accessible on Gadi using:

module use /g/data/vk83/prerelease/modules
module load access-om2/pr131-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-om2-pr131-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
Contributor

🚀 Attempted to deploy access-om2 Prerelease pr131-19 with commit 157f411

🖥️ Gadi Deployment ❌

@anton-seaice
Copy link
Collaborator Author

!redeploy

@github-actions
Copy link
Contributor

🚀 Attempted to deploy access-om2 Prerelease pr131-20 with commit 157f411

🖥️ Gadi Deployment ✔️

Usage Instructions

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

  • 2025.12.000 as a Release (when merged).
  • pr131-20 as a Prerelease (during this PR).

This Prerelease is accessible on Gadi using:

module use /g/data/vk83/prerelease/modules
module load access-om2/pr131-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-om2-pr131-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 merged !

@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