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

CABLE files reorganisation #52

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

Conversation

ccarouge
Copy link
Member

@ccarouge ccarouge commented Feb 28, 2025

This build should not change results. Only uses files in a different place. Used to check the movement of files doesn't break the build and doesn't break the run.


🚀 The latest prerelease access-esm1p6/pr52-7 at 800ea28 is here: #52 (comment) 🚀

Copy link

The model version in the spack.yaml has not been updated.
Either update it manually, or comment the following to have it updated and committed automatically:

  • !bump major for feature releases
  • !bump minor for bugfixes

@ccarouge
Copy link
Member Author

!bump minor

Copy link

✅ Version bumped from dev_2024.12.0 to 2024.12.1

Copy link

🚀 Deploying access-esm1.6 2024.12.1 as prerelease pr52-1 with commit a6b98ea

Details and usage instructions

This access-esm1.6 model will be deployed as:

  • 2024.12.1 as a Release (when merged).
  • pr52-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/pr52-1

where the binaries shall be on your $PATH.
This Prerelease is also accessible on Gadi via /g/data/vk83/prerelease/apps/spack/0.22/spack in the access-esm1p6-pr52-1 environment.

🛠️ Using: spack 0.22, spack-packages 2024.12.0, spack-config 2025.02.1

Details

It will be deployed using:

  • access-nri/spack on branch 0.22
  • access-nri/spack-packages version 2024.12.0
  • access-nri/spack-config version 2025.02.1

If this is not what was expected, commit changes to config/versions.json.

Copy link

🚀 Deploying access-esm1.6 2024.12.1 as prerelease pr52-2 with commit 462ea27

Details and usage instructions

This access-esm1.6 model will be deployed as:

  • 2024.12.1 as a Release (when merged).
  • pr52-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/pr52-2

where the binaries shall be on your $PATH.
This Prerelease is also accessible on Gadi via /g/data/vk83/prerelease/apps/spack/0.22/spack in the access-esm1p6-pr52-2 environment.

🛠️ Using: spack 0.22, spack-packages 2024.12.0, spack-config 2025.02.1

Details

It will be deployed using:

  • access-nri/spack on branch 0.22
  • access-nri/spack-packages version 2024.12.0
  • access-nri/spack-config version 2025.02.1

If this is not what was expected, commit changes to config/versions.json.

@ccarouge
Copy link
Member Author

@CodeGat There is a connection error with rsync which I don't think is on my side of things to fix, but I could be wrong.

But I've been able to get this far without help. And I even found the compilation error in the first test that was coming from my UM branch! Great hand-holding in the error messages from the CI to help with the setup of spack.yaml.

@ccarouge
Copy link
Member Author

ccarouge commented Mar 2, 2025

@CodeGat Maybe ignore previous message for now (unless you already know the cause). I need to scrape the UM branch because it isn't what I want.

Copy link

github-actions bot commented Mar 2, 2025

🚀 Deploying access-esm1.6 2024.12.1 as prerelease pr52-3 with commit fbd5018

Details and usage instructions

This access-esm1.6 model will be deployed as:

  • 2024.12.1 as a Release (when merged).
  • pr52-3 as a Prerelease (during this PR).

This Prerelease is accessible on Gadi using:

module use /g/data/vk83/prerelease/modules
module load access-esm1p6/pr52-3

where the binaries shall be on your $PATH.
This Prerelease is also accessible on Gadi via /g/data/vk83/prerelease/apps/spack/0.22/spack in the access-esm1p6-pr52-3 environment.

🛠️ Using: spack 0.22, spack-packages 2024.12.0, spack-config 2025.02.1

Details

It will be deployed using:

  • access-nri/spack on branch 0.22
  • access-nri/spack-packages version 2024.12.0
  • access-nri/spack-config version 2025.02.1

If this is not what was expected, commit changes to config/versions.json.

@ccarouge ccarouge temporarily deployed to Gadi Prerelease March 2, 2025 22:41 — with GitHub Actions Inactive
@CodeGat
Copy link
Member

CodeGat commented Mar 2, 2025

Hey @ccarouge, the rsync error is transient and seems to be related to the ssh connection to Gadi, as far as I can tell. Let me know if you need a hand with the Prerelease stuff :)

Copy link

github-actions bot commented Mar 3, 2025

🚀 Deploying access-esm1.6 dev_2025.03.01 as prerelease pr52-4 with commit 36e5a58

Details and usage instructions

This access-esm1.6 model will be deployed as:

  • dev_2025.03.01 as a Release (when merged).
  • pr52-4 as a Prerelease (during this PR).

This Prerelease is accessible on Gadi using:

module use /g/data/vk83/prerelease/modules
module load access-esm1p6/pr52-4

where the binaries shall be on your $PATH.
This Prerelease is also accessible on Gadi via /g/data/vk83/prerelease/apps/spack/0.22/spack in the access-esm1p6-pr52-4 environment.

🛠️ Using: spack 0.22, spack-packages 2024.12.0, spack-config 2025.02.1

Details

It will be deployed using:

  • access-nri/spack on branch 0.22
  • access-nri/spack-packages version 2024.12.0
  • access-nri/spack-config version 2025.02.1

If this is not what was expected, commit changes to config/versions.json.

@ccarouge ccarouge temporarily deployed to Gadi Prerelease March 3, 2025 22:06 — with GitHub Actions Inactive
@ccarouge
Copy link
Member Author

ccarouge commented Mar 3, 2025

@CodeGat When are the deployed pre-release removed? Currently, the latest pre-release for this PR is pr52-4. Is pr52-3 already deleted? I want to know if I can deploy 2 versions at once from a PR or if I need 2 PRs, because I need to compare this one with the same exe but built from UM's main. In short, make sure only the UM commit hash is different.

@CodeGat
Copy link
Member

CodeGat commented Mar 3, 2025

@ccarouge Prereleases are deleted when a pull request is closed, so the existing Prereleases should still be there!

@aidanheerdegen
Copy link
Member

Also note if you make your PR a draft the CI checks are a little less picky, e.g. it doesn't bug you about versions.

@ccarouge ccarouge marked this pull request as draft March 4, 2025 02:21
@ccarouge
Copy link
Member Author

ccarouge commented Mar 4, 2025

Prereleases are deleted when a pull request is closed, so the existing Prereleases should still be there!

@bschroeter This means you can use this PR to build the prerelease with the shuffle and from main if you want, instead of opening 2 PRs. Your choice, depends if you think you'll get confused between version numbers or not.

@CodeGat CodeGat force-pushed the 51-Reorganising-CABLE-files branch from 36e5a58 to f65e4bd Compare March 6, 2025 02:23
Switching UM7 to the head of main for bitwise comparison.
@bschroeter bschroeter temporarily deployed to Gadi Prerelease March 6, 2025 02:30 — with GitHub Actions Inactive
Copy link

github-actions bot commented Mar 6, 2025

🚀 Attempted to deploy access-esm1p6 Prerelease pr52-5 with commit ffb4b5c

🖥️ Gadi Deployment ✔️

Usage Instructions

This access-esm1.6 model will be deployed to Gadi as:

  • dev_2025.03.01 as a Release (when merged).
  • pr52-5 as a Prerelease (during this PR).

This Prerelease is accessible on Gadi using:

module use /g/data/vk83/prerelease/modules
module load access-esm1p6/pr52-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-esm1p6-pr52-5 environment.

Configuration Information

This Prerelease is deployed using:

  • access-nri/spack on branch 0.22
  • access-nri/spack-packages version 2024.12.0
  • access-nri/spack-config version 2025.02.1

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

Copy link

🚀 Attempted to deploy access-esm1p6 Prerelease pr52-6 with commit b66192c

🖥️ Gadi Deployment ❌

Reconcile version differences due to merge.
Copy link

🚀 Attempted to deploy access-esm1p6 Prerelease pr52-6 with commit 1864b6c

🖥️ Gadi Deployment ✔️

Usage Instructions

This access-esm1.6 model will be deployed to Gadi as:

  • dev_2025.03.01 as a Release (when merged).
  • pr52-6 as a Prerelease (during this PR).

This Prerelease is accessible on Gadi using:

module use /g/data/vk83/prerelease/modules
module load access-esm1p6/pr52-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-esm1p6-pr52-6 environment.

Configuration Information

This Prerelease is deployed using:

  • access-nri/spack on branch 0.22
  • access-nri/spack-packages version 2025.03.002
  • access-nri/spack-config version 2025.02.2

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

Rolled back to previously working versions of packages with new hash for shuffled UM7
Copy link

🚀 Attempted to deploy access-esm1p6 Prerelease pr52-7 with commit 800ea28

🖥️ Gadi Deployment ✔️

Usage Instructions

This access-esm1.6 model will be deployed to Gadi as:

  • dev_2025.03.01 as a Release (when merged).
  • pr52-7 as a Prerelease (during this PR).

This Prerelease is accessible on Gadi using:

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

Configuration Information

This Prerelease is deployed using:

  • access-nri/spack on branch 0.22
  • access-nri/spack-packages version 2025.03.002
  • access-nri/spack-config version 2025.02.2

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
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants