Skip to content

Update coupled names debug#212

Draft
ashjbarnes wants to merge 48 commits intomainfrom
update-coupled-names-debug
Draft

Update coupled names debug#212
ashjbarnes wants to merge 48 commits intomainfrom
update-coupled-names-debug

Conversation

@ashjbarnes
Copy link
Collaborator

@ashjbarnes ashjbarnes commented Mar 19, 2026

same as Kieran's latest build but with debug flags on everything. Currently running this regionally gets an opaque segfault, I suspect somewhere in CMEPS or elsewhere in access share repos


🚀 The latest prerelease access-om3/pr212-1 at 4c794d2 is here: #212 (comment) 🚀

@ashjbarnes ashjbarnes requested a review from a team as a code owner March 19, 2026 01:33
@ashjbarnes
Copy link
Collaborator Author

!redeploy

@anton-seaice anton-seaice marked this pull request as draft March 19, 2026 01:54
@github-actions
Copy link

🚀 Attempted to deploy access-om3 Prerelease pr212-1 with commit 4c794d2

🖥️ Gadi Deployment ✔️

Usage Instructions

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

  • 2025.08.999 as a Release (when merged).
  • pr212-1 as a Prerelease (during this PR).

This Prerelease is accessible on Gadi using:

module use /g/data/vk83/prerelease/modules
module load access-om3/pr212-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-om3-pr212-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, 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.

2 participants