Skip to content

Change target from x86_64 to x86_64_v4#69

Merged
harshula merged 1 commit into
mainfrom
development
Jun 2, 2026
Merged

Change target from x86_64 to x86_64_v4#69
harshula merged 1 commit into
mainfrom
development

Conversation

@harshula

@harshula harshula commented May 29, 2026

Copy link
Copy Markdown
Collaborator
  • A number of ACCESS models have changed the target to x86_64_v4
  • Spack removes the single quotes when re-writing the spack.yaml

🚀 The latest prerelease access-test/pr69-4 at 7ae11ea is here: #69 (comment) 🚀

@harshula harshula self-assigned this May 29, 2026
@github-actions

Copy link
Copy Markdown

The model version in the spack.yaml has not been updated.
You can update it manually.
Alternatively, comment the following to have it updated and committed automatically:

  • !bump major for feature releases
  • !bump minor for bugfixes

@github-actions

Copy link
Copy Markdown

🚀 Attempted to deploy access-test Prerelease pr69-1 with commit 4b88268

🖥️ Gadi Deployment ❌

@github-actions

Copy link
Copy Markdown

🚀 Attempted to deploy access-test Prerelease pr69-1 with commit 6db75e1

🖥️ Gadi Deployment ❌

@harshula

Copy link
Copy Markdown
Collaborator Author

This PR requires ACCESS-NRI/access-spack-packages#432 .

@harshula harshula temporarily deployed to Gadi Prerelease May 29, 2026 04:15 — with GitHub Actions Inactive
@github-actions

Copy link
Copy Markdown

🚀 Attempted to deploy access-test Prerelease pr69-2 with commit 89c56c9

🖥️ Gadi Deployment ✔️

Usage Instructions

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

  • 2026.01.002 as a Release (when merged).
  • pr69-2 as a Prerelease (during this PR).

This Prerelease is accessible on Gadi using:

module use /g/data/vk83/prerelease/modules
module load access-test/pr69-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-test-pr69-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 2026.05.003
  • access-nri/spack-config version 2026.05.004

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.

@harshula harshula force-pushed the development branch 4 times, most recently from 2b5493f to f6c3a98 Compare May 29, 2026 04:38
@github-actions

Copy link
Copy Markdown

🚀 Attempted to deploy access-test Prerelease pr69-3 with commit f9c4f7e

🖥️ Gadi Deployment ❌

@harshula harshula temporarily deployed to Gadi Prerelease May 29, 2026 04:45 — with GitHub Actions Inactive
@github-actions

Copy link
Copy Markdown

🚀 Attempted to deploy access-test Prerelease pr69-3 with commit f6c3a98

🖥️ Gadi Deployment ✔️

Usage Instructions

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

  • 2026.05.000 as a Release (when merged).
  • pr69-3 as a Prerelease (during this PR).

This Prerelease is accessible on Gadi using:

module use /g/data/vk83/prerelease/modules
module load access-test/pr69-3

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-test-pr69-3 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 2026.05.003
  • access-nri/spack-config version 2026.05.004

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.

* A number of ACCESS models have changed the target to x86_64_v4
* Use the latest openmpi available on Gadi.
* Need access-spack-packages 2026.05.003
@github-actions

github-actions Bot commented Jun 2, 2026

Copy link
Copy Markdown

🚀 Attempted to deploy access-test Prerelease pr69-4 with commit 7ae11ea

🖥️ Gadi Deployment ✔️

Usage Instructions

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

  • 2026.06.000 as a Release (when merged).
  • pr69-4 as a Prerelease (during this PR).

This Prerelease is accessible on Gadi using:

module use /g/data/vk83/prerelease/modules
module load access-test/pr69-4

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-test-pr69-4 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 2026.05.003
  • access-nri/spack-config version 2026.05.004

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.

@harshula harshula merged commit b7fd5e7 into main Jun 2, 2026
9 checks passed
@github-project-automation github-project-automation Bot moved this from New Issues 🌅 to Done ✅ in Model Release Jun 2, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

Status: Done ✅

Development

Successfully merging this pull request may close these issues.

3 participants