Skip to content

Add the latest commit on the CICE5 branch; does not need the params at compile-time - #221

Draft
manodeep wants to merge 1 commit into
mainfrom
220-test-cice5-runtime-params
Draft

Add the latest commit on the CICE5 branch; does not need the params at compile-time#221
manodeep wants to merge 1 commit into
mainfrom
220-test-cice5-runtime-params

Conversation

@manodeep

@manodeep manodeep commented Aug 17, 2026

Copy link
Copy Markdown
Collaborator

Deploying for testing (ie bitwise repro) the CICE5 runtime params feature


🚀 The latest prerelease access-esm1p6/pr221-2 at 61013e9 is here: #221 (comment) 🚀

@manodeep
manodeep marked this pull request as draft August 17, 2026 00:06
@manodeep

Copy link
Copy Markdown
Collaborator Author

Marking as draft for versioning reasons ...

@github-actions

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

Copy link
Copy Markdown

🚀 Attempted to deploy access-esm1p6 Prerelease pr221-1 with commit 9987118

🖥️ Gadi Deployment ❌

@manodeep
manodeep temporarily deployed to Gadi Prerelease August 17, 2026 00:09 — with GitHub Actions Inactive
@github-actions

Copy link
Copy Markdown

🚀 Attempted to deploy access-esm1p6 Prerelease pr221-1 with commit 9987118

🖥️ Gadi Deployment ✔️

Usage Instructions

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

  • 2026.04.001 as a Release (when merged).
  • pr221-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/pr221-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-esm1p6-pr221-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.004
  • 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
manodeep force-pushed the 220-test-cice5-runtime-params branch from 9987118 to 61013e9 Compare August 25, 2026 01:27
@manodeep

Copy link
Copy Markdown
Collaborator Author

Rebased with the latest main - @micaeljtoliveira

@manodeep
manodeep temporarily deployed to Gadi Prerelease August 25, 2026 01:30 — with GitHub Actions Inactive
@github-actions

Copy link
Copy Markdown

🚀 Attempted to deploy access-esm1p6 Prerelease pr221-2 with commit 61013e9

🖥️ Gadi Deployment ✔️

Usage Instructions

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

  • 2026.04.002 as a Release (when merged).
  • pr221-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/pr221-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-esm1p6-pr221-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.08.009
  • 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.

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