Skip to content
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.

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

test - remove mom symmetric #42

Draft
wants to merge 2 commits into
base: main
Choose a base branch
from
Draft

Conversation

minghangli-uni
Copy link

@minghangli-uni minghangli-uni commented Feb 6, 2025

Test building access-om3 without mom symmetric


🚀 The latest prerelease access-om3/pr42-2 at 52dac81 is here: #42 (comment) 🚀

Copy link

github-actions bot commented Feb 6, 2025

🚀 Attempted to deploy access-om3 Prerelease pr42-1 with commit 24b5529

🖥️ Gadi Deployment ❌

Copy link

github-actions bot commented Feb 6, 2025

🚀 Attempted to deploy access-om3 Prerelease pr42-2 with commit 52dac81

🖥️ Gadi Deployment ✔️

Usage Instructions

This access-om3 model will be deployed to Gadi as:

  • 2025.01.restart_legacy as a Release (when merged).
  • pr42-2 as a Prerelease (during this PR).

This Prerelease is accessible on Gadi using:

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

Configuration Information

This Prerelease is deployed using:

  • access-nri/spack on branch 0.22
  • access-nri/spack-packages version 2024.07.08
  • access-nri/spack-config version 2025.01.1

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

@CodeGat
Copy link
Member

CodeGat commented Feb 6, 2025

Hey @minghangli-uni - just letting you know that in future, you shouldn't have to change the version of the spec if your pull request is a draft! 😄

@minghangli-uni
Copy link
Author

Ah I see, thanks @CodeGat

@anton-seaice
Copy link
Contributor

The first failure looked like a random filesystem failure to me

@minghangli-uni
Copy link
Author

yeah, seems like a longrun spack failure or an i/o load issue.

==> [2025-02-06-14:36:11.243294] Flagging esmf-git.v8.7.0=8.7.0-kn2zsgmc56vusenxtwyja64gbvkcwx5l as failed: Timed out waiting for a write lock after 60.081s.
    Made 161 attempts on file: /g/data/vk83/prerelease/apps/spack/0.22/release/.spack-db/lock

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.

3 participants