Skip to content

oneapi build using system openmpi modules - #71

Closed
CodeGat wants to merge 12 commits into
mainfrom
oneapi-build-new-spack-config
Closed

CodeGat wants to merge 12 commits into
mainfrom
oneapi-build-new-spack-config

Conversation

@CodeGat

@CodeGat CodeGat commented Oct 13, 2026 •

Copy link
Copy Markdown
Member

Based on #68


🚀 The latest prerelease access-am3/pr71-5 at 143fe5f is here: #71 (comment) 🚀

@CodeGat CodeGat self-assigned this Oct 13, 2026
@github-actions

Copy link
Copy Markdown

🚀 Attempted to deploy access-am3 Prerelease pr71-1 with commit 96e2890

🖥️ Gadi Deployment ❌

@CodeGat
CodeGat deployed to Gadi Prerelease October 13, 2026 03:21 — with GitHub Actions Active
@github-actions

Copy link
Copy Markdown

🚀 Attempted to deploy access-am3 Prerelease pr71-2 with commit dc551ff

🖥️ Gadi Deployment ✔️

Usage Instructions

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

  • 2026.10.000 as a Release (when merged).
  • pr71-2 as a Prerelease (during this PR).

This Prerelease is accessible on Gadi using:

module use /g/data/vk83/prerelease/modules
module load access-am3/pr71-2

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-am3-pr71-2 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:

  • access-nri/spack on branch 1.1
  • ACCESS-NRI/upstream-spack-packages version access/v1.1
  • access-nri/access-spack-packages version api-v2
  • access-nri/spack-config version 2026.10.002

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

@CodeGat CodeGat closed this Oct 13, 2026
@CodeGat
CodeGat deployed to Gadi Prerelease October 13, 2026 21:54 — with GitHub Actions Active
@CodeGat CodeGat reopened this Oct 14, 2026
@github-actions

Copy link
Copy Markdown

🚀 Attempted to deploy access-am3 Prerelease pr71-4 with commit dc551ff

🖥️ Gadi Deployment ❌

@CodeGat
CodeGat deployed to Gadi Prerelease October 14, 2026 05:14 — with GitHub Actions Active
@github-actions

Copy link
Copy Markdown

🚀 Attempted to deploy access-am3 Prerelease pr71-5 with commit 143fe5f

🖥️ Gadi Deployment ✔️

Usage Instructions

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

  • 2026.10.000 as a Release (when merged).
  • pr71-5 as a Prerelease (during this PR).

This Prerelease is accessible on Gadi using:

module use /g/data/vk83/prerelease/modules
module load access-am3/pr71-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/1.1/spack in the access-am3-pr71-5 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:

  • access-nri/spack on branch 1.1
  • ACCESS-NRI/upstream-spack-packages version access/v1.1
  • access-nri/access-spack-packages version api-v2
  • access-nri/spack-config version 2026.10.002

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

@CodeGat CodeGat closed this Oct 14, 2026
@CodeGat
CodeGat deployed to Gadi Prerelease October 14, 2026 23:55 — with GitHub Actions Active
@CodeGat
CodeGat deleted the oneapi-build-new-spack-config branch October 15, 2026 00:08

This branch was successfully deployed

1 active deployment
Gadi Prerelease — 143fe5fe Deployed Oct 14, 2026 by CodeGat via Closed / Undeploy access-am3-pr71-* from Gadi Prerelease #404
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.

2 participants