spack.yaml: update to openmpi 4.1.7

[anton-seaice]

Test openmpi 4.1.7

[github-actions]

🚀 Deploying access-om3 2024.11.b as prerelease pr20-1 with commit ff865a0

Details and usage instructions

This access-om3 model will be deployed as:

• 2024.11.b as a Release (when merged).
• pr20-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/pr20-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-om3- environment.

🛠️ Using: spack 0.22, spack-packages 2024.07.08, spack-config 2024.11.11

Details

It will be deployed using:

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

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

[anton-seaice]

@harshula @CodeGat - I guess we need to add openmpi 4.1.7 to the access-nri spack-config to use it ?

https://github.com/ACCESS-NRI/spack-config/blob/2ee50c69d2dfa9e024b47dc92d617f3aa7dcdd37/common/gadi/packages.yaml#L280

[harshula]

Hi @anton-seaice, The version of spack-config can no longer be modified by users via the model deployment repository.
Hi @CodeGat , I've reviewed and merged ACCESS-NRI/spack-config#49 and tagged it 2024.11.27.

[github-actions]

🚀 Deploying access-om3 2024.11.b as prerelease pr20-2 with commit 7a85258

Details and usage instructions

This access-om3 model will be deployed as:

• 2024.11.b as a Release (when merged).
• pr20-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/pr20-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-om3- environment.

🛠️ Using: spack 0.22, spack-packages 2024.07.08, spack-config 2024.11.27

Details

It will be deployed using:

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

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

[anton-seaice]

@benmenadue - I built & ran some code with openmpi 4.1.7, and it gives me lots of these messages (and runs) :

[gadi-cpu-clx-2975:103:3614375 - context.c:307][2024-11-28 17:03:48] ERROR failed to initialize sharp

Is this related to the new openmpi build? I'm pretty sure that the only thing that changed

[benmenadue]

@anton-seaice Yes, it's using a newer version of UCC that has support for SHARP. But we haven't set the needed bits for that up on the fabric yet. I was going to disable it at the module level for now but forgot, sorry. Using

mpirun -x UCC_TLS=^sharp

will silence those messages until I can update the module.

[anton-seaice]

Ok thanks - no worries

[CodeGat]

Hey, due to ACCESS-NRI/build-cd#173 we have had to update the infrastructure in this repository, as well - see #28.

We try and keep these kinds of updates to a minimum, and, starting from this one onwards, it will no longer be a hard requirement to update PR branches to incorporate infrastructure changes in order for the infrastructure to work - as you need to for this one.

To update this PR to the new origin/main, do the following:

git pull
git rebase origin/main
git push --force

to incorporate CI changes into the PR.

Your PR may redeploy, but that is okay - it should be identical to the last deployment. Let me know if you have any questions or issues.

[anton-seaice]

Deploying in #39