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

42 dev config #43

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

42 dev config #43

wants to merge 56 commits into from

Conversation

JhanSrbinovsky
Copy link
Collaborator

@JhanSrbinovsky JhanSrbinovsky commented Feb 12, 2025

see issue #42


🚀 The latest prerelease access-esm1p6/pr43-9 at 39d6679 is here: #43 (comment) 🚀

@JhanSrbinovsky JhanSrbinovsky linked an issue Feb 12, 2025 that may be closed by this pull request
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

@JhanSrbinovsky
Copy link
Collaborator Author

@blimlim arrggghhh - why is this failing? its just a straight up copy of SpinUp_b which has always worked, including today.

@blimlim
Copy link

blimlim commented Feb 12, 2025

Hi @JhanSrbinovsky!

The deployment system has different requirements depending on whether a pull request is marked as a draft or not, which I think is bringing up this error.

When a PR is not a draft, the deployment assumes that you're making a new release or new version of the model. In this case it requires the version number in

specs:
    - [email protected]_2024.12.0
...
projections:
          access-esm1p6: '{name}/dev_2024.12.0'

to be updated to something new.

For pull requests marked as drafts, this requirement doesn't apply and it will happily deploy prerelease executables without changes to the version number.

Is the goal to merge this PR into main? In this case, I'd try updating the version to dev_2025.02.0.

Otherwise if you're building some executables for testing, marking this PR as a draft should then let the build go ahead.

@JhanSrbinovsky JhanSrbinovsky marked this pull request as draft February 12, 2025 23:55
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

@blimlim
Copy link

blimlim commented Feb 13, 2025

!redeploy

Copy link

🚀 Deploying access-esm1.6 dev_2024.12.0 as prerelease pr43-1 with commit 087b6f2

Details and usage instructions

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

  • dev_2024.12.0 as a Release (when merged).
  • pr43-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/pr43-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-pr43-1 environment.

🛠️ Using: spack 0.22, spack-packages 2024.12.0, spack-config 2025.01.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.01.1

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

@JhanSrbinovsky JhanSrbinovsky self-assigned this Feb 13, 2025
@JhanSrbinovsky
Copy link
Collaborator Author

@blimlim - looks like the same error

@blimlim
Copy link

blimlim commented Feb 13, 2025

Hi @JhanSrbinovsky, I think the deployment itself was successful despite the messages from github! I've been able to load the modules listed:

module use /g/data/vk83/prerelease/modules
module load access-esm1p6/pr43-1

I think the Some checks were not successful message is just carrying over from earlier – @CodeGat is this correct?

@CodeGat
Copy link
Member

CodeGat commented Feb 13, 2025

Yeah. The failing check is from the initial deployment of the commit. The !redeployed commit succeeded.

The reason you're still seeing the red cross is because GitHub treats previous failed checks as a higher priority than new successes...bit of a quirk of GitHub!

@blimlim
Copy link

blimlim commented Feb 13, 2025

Thanks @CodeGat!

@JhanSrbinovsky
Copy link
Collaborator Author

Thanks for your help @blimlim & @CodeGat.

what did you to to get the redeploy to work @blimlim

@blimlim
Copy link

blimlim commented Feb 13, 2025

Redeploying is quite simple thanks to @CodeGat! You just have to add a comment saying "!redeploy"

@CodeGat
Copy link
Member

CodeGat commented Feb 13, 2025

Indeed. Its main use case was for redeploying changes to a git.BRANCH component, but since that isn't working at the moment the isn't as much reason to use it!

Copy link

🚀 Deploying access-esm1.6 dev_2024.12.0 as prerelease pr43-2 with commit 8f70ab1

Details and usage instructions

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

  • dev_2024.12.0 as a Release (when merged).
  • pr43-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/pr43-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-pr43-2 environment.

🛠️ Using: spack 0.22, spack-packages 2024.12.0, spack-config 2025.01.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.01.1

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

@JhanSrbinovsky
Copy link
Collaborator Author

!redeploy

Copy link

🚀 Deploying access-esm1.6 dev_2024.12.0 as prerelease pr43-3 with commit 8f70ab1

Details and usage instructions

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

  • dev_2024.12.0 as a Release (when merged).
  • pr43-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/pr43-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-pr43-3 environment.

🛠️ Using: spack 0.22, spack-packages 2024.12.0, spack-config 2025.01.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.01.1

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

Copy link

🚀 Deploying access-esm1.6 dev_2024.12.0 as prerelease pr43-4 with commit f987b9e

Details and usage instructions

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

  • dev_2024.12.0 as a Release (when merged).
  • pr43-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/pr43-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-pr43-4 environment.

🛠️ Using: spack 0.22, spack-packages 2024.12.0, spack-config 2025.01.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.01.1

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

Copy link

🚀 Deploying access-esm1.6 dev_2024.12.0 as prerelease pr43-5 with commit d2622bd

Details and usage instructions

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

  • dev_2024.12.0 as a Release (when merged).
  • pr43-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/pr43-5

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-pr43-5 environment.

🛠️ Using: spack 0.22, spack-packages 2024.12.0, spack-config 2025.01.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.01.1

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

Copy link

🚀 Deploying access-esm1.6 dev_2024.12.0 as prerelease pr43-6 with commit 4ac0c6a

Details and usage instructions

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

  • dev_2024.12.0 as a Release (when merged).
  • pr43-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/pr43-6

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-pr43-6 environment.

🛠️ Using: spack 0.22, spack-packages 2024.12.0, spack-config 2025.01.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.01.1

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

@JhanSrbinovsky JhanSrbinovsky mentioned this pull request Feb 19, 2025
@JhanSrbinovsky
Copy link
Collaborator Author

JhanSrbinovsky commented Feb 20, 2025

Active runs from dev-access-esm1,6 with varying runtime configs:
all have soil_thermal_fix =true

  1. LUH3restart - revised LUH3 based restart
  2. PI-case2e. - soil/veg params thru nmls
  3. PI-case-l_rev - L_rev_corr=true

@JhanSrbinovsky
Copy link
Collaborator Author

"LUH3 restart" output is AT

/scratch/p66/jxs599/access-esm/archive/dev-LUH3-restart-expt-5eed0c42

Copy link

🚀 Deploying access-esm1.6 dev_2024.12.0 as prerelease pr43-7 with commit 8083584

Details and usage instructions

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

  • dev_2024.12.0 as a Release (when merged).
  • pr43-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/pr43-7

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

@manodeep
Copy link

manodeep commented Mar 6, 2025

!redeploy

Copy link

github-actions bot commented Mar 6, 2025

🚀 Attempted to deploy access-esm1p6 Prerelease pr43-9 with commit 39d6679

🖥️ Gadi Deployment ✔️

Usage Instructions

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

  • dev_2024.12.0 as a Release (when merged).
  • pr43-9 as a Prerelease (during this PR).

This Prerelease is accessible on Gadi using:

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

dougiesquire added a commit that referenced this pull request Mar 6, 2025
See [this](#43 (comment)) and subsequent comments for justification
@JhanSrbinovsky
Copy link
Collaborator Author

Thanks @CodeGat. it rebased without error - but this PR updated way less than #48

dougiesquire added a commit that referenced this pull request Mar 11, 2025
* Use latest gtracers, FMS and MOM5 dev tags

* Use latest CICE from update_DaveBi branch

* Use latest UM from dev-access-esm1.6 branch. See [this](#43 (comment)) and subsequent comments for justification

* Use oasis3-mct access-esm1.5-2025.03.001

* Update to spack-packages 2025.03.002
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.

dev-config
6 participants