Building from UM7 repo

[Jhan]

Nope. Forbidden

[harshula]

Hi @Jhan, Sounds good. Let’s meet at 1pm. I’ll send the Zoom link via a private message.

[atteggiani (Davide Marchegiani, ACCESS-NRI Atmospheric team)]

@anton

@harshula - I think these instructions have the arguments in the wrong order ?

Yes, you are right.

Will update the instructions.
Thank you for finding out!

[harshula]

Jhan created a Pre-release build that’s available for testing: Update cable3 by JhanSrbinovsky · Pull Request #5 · ACCESS-NRI/ACCESS-ESM1.6 · GitHub

[harshula]

The latest instructions for running the Pre-release build are here: Update cable3 by JhanSrbinovsky · Pull Request #5 · ACCESS-NRI/ACCESS-ESM1.6 · GitHub

[TommyGatti]

So for future updates to the above prerelease, you would update the UM source code, and then to trigger another prerelease with those changes, you would add another commit to the ACCESS-ESM1.6 PR, since the workflow runs on updates to the pull request. The commit can be:

• Just adding a comment to the spack.yaml noting the particular hash of the HEAD of the UM branch
• Or even an empty commit where the message is why it’s being rebuilt: git commit --allow-empty -m "Rebuilt to test these new UM changes"

This all assumes that you’ll be using a branch reference rather than a tag - if you’re using a tag then the workflow would be to just update the spack.yaml with the new tag each time!

[Jhan]

Great Thanks Tommy. I’ll try it out. IF there is a bug in the UM code modification that stops the compile, where will I find this?

[Jhan]

bump

[Aidan (Aidan Heerdegen, ACCESS-NRI Release Team Lead)]

@Jhan

IF there is a bug in the UM code modification that stops the compile, where will I find this?

The workflow will have an error condition, e.g. see this ESM1.5 build:

github-actions[bot]

Click on the Red Cross to see the status

and then click on the “Details” link to see the detail of the output from the commands that failed.