Skip to content

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

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Draft
anton-seaice wants to merge 8 commits into
base: main
Choose a base branch
from
Draft

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

anton-seaice wants to merge 8 commits into from

Conversation

@anton-seaice
Copy link
Collaborator

@anton-seaice anton-seaice commented Jan 5, 2026 •
edited by github-actions bot
Loading

🚀 The latest prerelease access-om2/pr131-9 at 663fb44 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

anton-seaice commented Jan 5, 2026

!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.

@anton-seaice anton-seaice deployed to Gadi Prerelease January 9, 2026 03:19 — with GitHub Actions Active
@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.

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

Reviewers

No reviews

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

2 participants

@anton-seaice