Skip to content

Build with oneapi - #68

Open
Whyborn wants to merge 11 commits into
developmentfrom
oneapi-build
Open

Whyborn wants to merge 11 commits into
developmentfrom
oneapi-build

Conversation

@Whyborn

@Whyborn Whyborn commented Oct 2, 2026 •

Copy link
Copy Markdown
Collaborator

Update the compiler to use the Oneapi compiler. Includes updated GCOM build.


🚀 The latest prerelease access-am3/pr68-12 at 415f530 is here: #68 (comment) 🚀

@Whyborn
Whyborn deployed to Gadi Prerelease October 2, 2026 00:28 — with GitHub Actions Active
@github-actions

github-actions Bot commented Oct 2, 2026

Copy link
Copy Markdown

🚀 Attempted to deploy access-am3 Prerelease pr68-1 with commit c17c976

🖥️ Gadi Deployment ❌

@github-actions

github-actions Bot commented Oct 2, 2026

Copy link
Copy Markdown

🚀 Attempted to deploy access-am3 Prerelease pr68-1 with commit c370fd6

🖥️ Gadi Deployment ❌

@github-actions

github-actions Bot commented Oct 2, 2026

Copy link
Copy Markdown

🚀 Attempted to deploy access-am3 Prerelease pr68-2 with commit 0394abb

🖥️ Gadi Deployment ✔️

Usage Instructions

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

  • 2026.10.000 as a Release (when merged).
  • pr68-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/pr68-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-pr68-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.08.001

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.

@Whyborn

Whyborn commented Oct 5, 2026

Copy link
Copy Markdown
Collaborator Author

Here's the PR deploying the oneapi build @MartinDix

@github-actions

Copy link
Copy Markdown

🚀 Attempted to deploy access-am3 Prerelease pr68-4 with commit d73e7b3

🖥️ Gadi Deployment ❌

@github-actions

Copy link
Copy Markdown

🚀 Attempted to deploy access-am3 Prerelease pr68-5 with commit a4e1767

🖥️ Gadi Deployment ❌

@github-actions

Copy link
Copy Markdown

🚀 Attempted to deploy access-am3 Prerelease pr68-6 with commit 40a68ff

🖥️ Gadi Deployment ❌

@github-actions

Copy link
Copy Markdown

🚀 Attempted to deploy access-am3 Prerelease pr68-7 with commit a5d2012

🖥️ Gadi Deployment ✔️

Usage Instructions

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

  • 2026.10.000 as a Release (when merged).
  • pr68-7 as a Prerelease (during this PR).

This Prerelease is accessible on Gadi using:

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

  • 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.000

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.

@github-actions

Copy link
Copy Markdown

🚀 Attempted to deploy access-am3 Prerelease pr68-8 with commit cb4b0df

🖥️ Gadi Deployment ✔️

Usage Instructions

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

  • 2026.10.000 as a Release (when merged).
  • pr68-8 as a Prerelease (during this PR).

This Prerelease is accessible on Gadi using:

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

  • 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.003

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.

@Whyborn
Whyborn deployed to Gadi Prerelease October 15, 2026 22:54 — with GitHub Actions Active
@github-actions

Copy link
Copy Markdown

🚀 Attempted to deploy access-am3 Prerelease pr68-9 with commit db3cffd

🖥️ Gadi Deployment ✔️

Usage Instructions

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

  • 2026.10.000 as a Release (when merged).
  • pr68-9 as a Prerelease (during this PR).

This Prerelease is accessible on Gadi using:

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

  • 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.003

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.

@Whyborn
Whyborn deployed to Gadi Prerelease October 16, 2026 00:15 — with GitHub Actions Active
@github-actions

Copy link
Copy Markdown

🚀 Attempted to deploy access-am3 Prerelease pr68-10 with commit 1a2c29b

🖥️ Gadi Deployment ✔️

Usage Instructions

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

  • 2026.10.000 as a Release (when merged).
  • pr68-10 as a Prerelease (during this PR).

This Prerelease is accessible on Gadi using:

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

  • 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.003

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.

@github-actions

Copy link
Copy Markdown

🚀 Attempted to deploy access-am3 Prerelease pr68-11 with commit 152f96d

🖥️ Gadi Deployment ✔️

Usage Instructions

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

  • 2026.10.000 as a Release (when merged).
  • pr68-11 as a Prerelease (during this PR).

This Prerelease is accessible on Gadi using:

module use /g/data/vk83/prerelease/modules
module load access-am3/pr68-11

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-pr68-11 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.003

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.

@Whyborn
Whyborn changed the base branch from main to development October 21, 2026 04:50
@Whyborn

Whyborn commented Oct 27, 2026

Copy link
Copy Markdown
Collaborator Author

!redeploy

@github-actions

Copy link
Copy Markdown

🚀 Attempted to deploy access-am3 Prerelease pr68-12 with commit 415f530

🖥️ Gadi Deployment ✔️

Usage Instructions

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

  • 2026.10.000 as a Release (when merged).
  • pr68-12 as a Prerelease (during this PR).

This Prerelease is accessible on Gadi using:

module use /g/data/vk83/prerelease/modules
module load access-am3/pr68-12

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-pr68-12 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.003

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.

This branch was successfully deployed

1 active (outdated) deployment
Gadi Prerelease — 152f96d5 Deployed Oct 20, 2026 by Whyborn via CI / Deploy (Gadi) / Gadi: Deployment #408
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.

1 participant