Thanks to visit codestin.com
Credit goes to github.com

Skip to content

Build packages for development#179

Draft
anton-seaice wants to merge 13 commits into
mainfrom
packages
Draft

Build packages for development#179
anton-seaice wants to merge 13 commits into
mainfrom
packages

Conversation

@anton-seaice

@anton-seaice anton-seaice commented Jan 14, 2026 •
edited by github-actions Bot
Loading

Copy link
Copy Markdown
Collaborator

🚀 The latest prerelease access-om3/pr179-14 at cac52bb is here: #179 (comment) 🚀

@github-actions

github-actions Bot commented Jan 15, 2026

Copy link
Copy Markdown

🚀 Attempted to deploy access-om3 Prerelease pr179-1 with commit d8214e6

🖥️ Gadi Deployment ✔️

Usage Instructions

access-om3, defined in ./spack.yaml, will be deployed to Gadi as:

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

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-pr179-1 environment.
Due to inode-saving measures, one will have to manually untar the environment metadata before environment activation with tar -xf .spack-env .spack-env.tar. It will require one to have write privileges.

Configuration Information

This Prerelease is deployed using:

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

@github-actions

github-actions Bot commented Jan 15, 2026

Copy link
Copy Markdown

🚀 Attempted to deploy access-om3 Prerelease pr179-2 with commit 93c15f9

🖥️ Gadi Deployment ❌

@github-actions

github-actions Bot commented Jan 15, 2026

Copy link
Copy Markdown

🚀 Attempted to deploy access-om3 Prerelease pr179-3 with commit 86d3759

🖥️ Gadi Deployment ❌

@github-actions

github-actions Bot commented Jan 15, 2026

Copy link
Copy Markdown

🚀 Attempted to deploy access-om3 Prerelease pr179-3 with commit 29bffea

🖥️ Gadi Deployment ❌

@anton-seaice

anton-seaice commented Jan 15, 2026

Copy link
Copy Markdown
Collaborator Author

!redeploy

@github-actions

github-actions Bot commented Jan 15, 2026

Copy link
Copy Markdown

🚀 Attempted to deploy access-om3 Prerelease pr179-5 with commit 86d3759

🖥️ Gadi Deployment ❌

@anton-seaice

anton-seaice commented Jan 15, 2026

Copy link
Copy Markdown
Collaborator Author

!redeploy

@github-actions

github-actions Bot commented Jan 15, 2026

Copy link
Copy Markdown

🚀 Attempted to deploy access-om3 Prerelease pr179-6 with commit 86d3759

🖥️ Gadi Deployment ❌

@github-actions

github-actions Bot commented Jan 15, 2026

Copy link
Copy Markdown

🚀 Attempted to deploy access-om3 Prerelease pr179-7 with commit 1ad52ec

🖥️ Gadi Deployment ✔️

Usage Instructions

access-om3, defined in ./spack.yaml, will be deployed to Gadi as:

  • 2025.08.001 as a Release (when merged).
  • pr179-7 as a Prerelease (during this PR).

This Prerelease is accessible on Gadi using:

module use /g/data/vk83/prerelease/modules
module load access-om3/pr179-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-om3-pr179-7 environment.
Due to inode-saving measures, one will have to manually untar the environment metadata before environment activation with tar -xf .spack-env .spack-env.tar. It will require one to have write privileges.

Configuration Information

This Prerelease is deployed using:

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

@anton-seaice

anton-seaice commented Jan 16, 2026 •
edited
Loading

Copy link
Copy Markdown
Collaborator Author

179-1: ~openmp

  -   ncr7xga          ^[email protected]%[email protected] cflags='-march=sapphirerapids -mtune=sapphirerapids -unroll' cxxflags='-unroll -march=sapphirerapids -mtune=sapphirerapids' fflags='-mtune=sapphirerapids -march=sapphirerapids -unroll' +access3~asymmetric_mem~ipo~openmp build_system=cmake build_type=Release generator=make arch=linux-rocky8-x86_64_v4

179-4: +openmp

 -   wh4kgid          ^[email protected]%[email protected] cflags='-mtune=sapphirerapids -march=sapphirerapids -unroll' cxxflags='-march=sapphirerapids -unroll -mtune=sapphirerapids' fflags='-march=sapphirerapids -unroll -mtune=sapphirerapids' +access3~asymmetric_mem~ipo+openmp build_system=cmake build_type=Release generator=make arch=linux-rocky8-x86_64_v4

179-7: ~openmp

 -   racv7bs          ^[email protected]%[email protected] cflags='-march=sapphirerapids -mtune=sapphirerapids -unroll' cxxflags='-march=sapphirerapids -mtune=sapphirerapids -unroll' fflags='-unroll -mtune=sapphirerapids -march=sapphirerapids' +access3~asymmetric_mem~ipo~openmp build_system=cmake build_type=Release generator=make arch=linux-rocky8-x86_64_v4

It appears to openmp variant is set randomly ?

?

@dougiesquire

dougiesquire commented Jan 16, 2026 •
edited
Loading

Copy link
Copy Markdown
Collaborator

I wonder if this because we have in MOM6 SPR:

variant("openmp", default=False, description="Enable OpenMP")

but in FMS SPR:

variant("openmp", default=True, description="Use OpenMP")

And we don't explicitly set anywhere. Maybe we want to explicitly set ~openmp when building MOM6? EDIT: could add to here?

@dougiesquire

dougiesquire commented Jan 16, 2026

Copy link
Copy Markdown
Collaborator

Kinda worrying that Spack's not deterministic with this though (ping @aidanheerdegen)

@anton-seaice

anton-seaice commented Jan 16, 2026 •
edited
Loading

Copy link
Copy Markdown
Collaborator Author

Ah - so probably when I added FMS to the spec, it changed the meaning ?

@dougiesquire

dougiesquire commented Jan 16, 2026 •
edited
Loading

Copy link
Copy Markdown
Collaborator

Ah - so probably when I added FMS to the spec, it changed the meaning ?

Oh, I missed that you'd done that sorry. Yeah possibly.

@github-actions

github-actions Bot commented Jan 29, 2026

Copy link
Copy Markdown

🚀 Attempted to deploy access-om3 Prerelease pr179-8 with commit eff6341

🖥️ Gadi Deployment ✔️

Usage Instructions

access-om3, defined in ./spack.yaml, will be deployed to Gadi as:

  • 2025.08.001 as a Release (when merged).
  • pr179-8 as a Prerelease (during this PR).

This Prerelease is accessible on Gadi using:

module use /g/data/vk83/prerelease/modules
module load access-om3/pr179-8

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-pr179-8 environment.
Due to inode-saving measures, one will have to manually untar the environment metadata before environment activation with tar -xf .spack-env .spack-env.tar. It will require one to have write privileges.

Configuration Information

This Prerelease is deployed using:

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

@github-actions

github-actions Bot commented Feb 5, 2026

Copy link
Copy Markdown

🚀 Attempted to deploy access-om3 Prerelease pr179-9 with commit 9ddf04c

🖥️ Gadi Deployment ✔️

Usage Instructions

access-om3, defined in ./spack.yaml, will be deployed to Gadi as:

  • 2025.08.001 as a Release (when merged).
  • pr179-9 as a Prerelease (during this PR).

This Prerelease is accessible on Gadi using:

module use /g/data/vk83/prerelease/modules
module load access-om3/pr179-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-om3-pr179-9 environment.
Due to inode-saving measures, one will have to manually untar the environment metadata before environment activation with tar -xf .spack-env .spack-env.tar. It will require one to have write privileges.

Configuration Information

This Prerelease is deployed using:

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

@github-actions

github-actions Bot commented Feb 17, 2026

Copy link
Copy Markdown

🚀 Attempted to deploy access-om3 Prerelease pr179-10 with commit 551e4c1

🖥️ Gadi Deployment ✔️

Usage Instructions

access-om3, defined in ./spack.yaml, will be deployed to Gadi as:

  • 2025.08.001 as a Release (when merged).
  • pr179-10 as a Prerelease (during this PR).

This Prerelease is accessible on Gadi using:

module use /g/data/vk83/prerelease/modules
module load access-om3/pr179-10

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-pr179-10 environment.
Due to inode-saving measures, one will have to manually untar the environment metadata before environment activation with tar -xf .spack-env .spack-env.tar. It will require one to have write privileges.

Configuration Information

This Prerelease is deployed using:

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

@github-actions

github-actions Bot commented Mar 3, 2026

Copy link
Copy Markdown

🚀 Attempted to deploy access-om3 Prerelease pr179-11 with commit cf70011

🖥️ Gadi Deployment ❌

@github-actions

github-actions Bot commented Mar 31, 2026

Copy link
Copy Markdown

🚀 Attempted to deploy access-om3 Prerelease pr179-12 with commit 36f1db2

🖥️ Gadi Deployment ❌

@github-actions

github-actions Bot commented Mar 31, 2026

Copy link
Copy Markdown

🚀 Attempted to deploy access-om3 Prerelease pr179-13 with commit 803fbea

🖥️ Gadi Deployment ❌

@github-actions

github-actions Bot commented Mar 31, 2026

Copy link
Copy Markdown

🚀 Attempted to deploy access-om3 Prerelease pr179-14 with commit cac52bb

🖥️ Gadi Deployment ✔️

Usage Instructions

access-om3, defined in spack.yaml, will be deployed to Gadi as:

  • 2026.03.000 as a Release (when merged).
  • pr179-14 as a Prerelease (during this PR).

This Prerelease is accessible on Gadi using:

module use /g/data/vk83/prerelease/modules
module load access-om3/pr179-14

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/1.1/spack in the access-om3-pr179-14 environment.
Due to inode-saving measures, one will have to manually untar the environment metadata before environment activation with tar -xf .spack-env .spack-env.tar. It will require one to have write privileges.

Configuration Information

This Prerelease is deployed using:

If the above was not what was expected, commit changes to config/versions.json in this PR, or propose changes to build-cds config/settings.json.

@aidanheerdegen

aidanheerdegen commented Apr 1, 2026

Copy link
Copy Markdown
Member

Kinda worrying that Spack's not deterministic with this though (ping @aidanheerdegen)

Soz, only just seen this.

Are we still concerned?

@anton-seaice

anton-seaice commented Apr 1, 2026

Copy link
Copy Markdown
Collaborator Author

Not enough to spend time on no

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

3 participants

@anton-seaice @dougiesquire @aidanheerdegen