Skip to content

Test to check module projections#53

Closed
aidanheerdegen wants to merge 9 commits intomainfrom
test-module-projections
Closed

Test to check module projections#53
aidanheerdegen wants to merge 9 commits intomainfrom
test-module-projections

Conversation

@aidanheerdegen
Copy link
Copy Markdown
Member

@aidanheerdegen aidanheerdegen commented Jul 31, 2025 •
edited by github-actions bot
Loading

Just testing the updated module projections

🚀 The latest prerelease access-test/pr53-6 at 9161832 is here: #53 (comment) 🚀

@github-actions
Copy link
Copy Markdown

github-actions bot commented Jul 31, 2025

🚀 Attempted to deploy access-test Prerelease pr53-1 with commit 389d5aa

🖥️ Gadi Deployment ❌

@github-actions
Copy link
Copy Markdown

github-actions bot commented Jul 31, 2025

🚀 Attempted to deploy access-test Prerelease pr53-1 with commit 591563c

🖥️ Gadi Deployment ❌

@aidanheerdegen aidanheerdegen mentioned this pull request Jul 31, 2025
Closed
@aidanheerdegen
Copy link
Copy Markdown
Member Author

aidanheerdegen commented Jul 31, 2025

Note this doesn't currently work

$ module load access-test/pr51-5
Loading access-test/pr51-5
  ERROR: Unable to locate a modulefile for 'access-test-component/pr51-5/main-joh6ivi'
  ERROR: Load of requirement access-test-component/pr51-5/main-joh6ivi failed

@CodeGat
Copy link
Copy Markdown
Member

CodeGat commented Jul 31, 2025

@aidanheerdegen there are a few more refs that you have to change - that one was just for CD, but there are a few in the ci.yml that need changing too

@github-actions
Copy link
Copy Markdown

github-actions bot commented Jul 31, 2025

🚀 Attempted to deploy access-test Prerelease pr53-1 with commit 002a136

🖥️ Gadi Deployment ❌

@github-actions
Copy link
Copy Markdown

github-actions bot commented Jul 31, 2025

🚀 Attempted to deploy access-test Prerelease pr53-1 with commit 63e8ad6

🖥️ Gadi Deployment ✔️

Usage Instructions

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

  • 2025.06.001 as a Release (when merged).
  • pr53-1 as a Prerelease (during this PR).

This Prerelease is accessible on Gadi using:

module use /g/data/vk83/prerelease/modules
module load access-test/pr53-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-test-pr53-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:

  • access-nri/spack on branch 0.22
  • access-nri/spack-packages version main
  • access-nri/spack-config version 2025.07.001

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

@aidanheerdegen
Copy link
Copy Markdown
Member Author

aidanheerdegen commented Jul 31, 2025

Still doesn't work.

The module creation failed:

https://github.com/ACCESS-NRI/ACCESS-TEST/actions/runs/16640335550/job/47089381133#step:15:358

==> [2025-07-31-15:09:31.378888] Updating view at /g/data/vk83/prerelease/apps/spack/0.22/environments/access-test-pr53-1/.spack-env/view
==> Warning: some module files could not be written
/g/data/vk83/prerelease/apps/spack/0.22/release/modules/linux-rocky8-x86_64/access-test/pr53-1/access-test-component/main-joh6ivi: [Errno 20] Not a directory: '/g/data/vk83/prerelease/apps/spack/0.22/release/modules/linux-rocky8-x86_64/access-test/pr53-1/access-test-component'
/g/data/vk83/prerelease/apps/spack/0.22/release/modules/linux-rocky8-x86_64/access-test/pr53-1/openmpi/4.1.5-qg5spmh: [Errno 20] Not a directory: '/g/data/vk83/prerelease/apps/spack/0.22/release/modules/linux-rocky8-x86_64/access-test/pr53-1/openmpi'

And interestingly this didn't fail the job, which it probably should.

@CodeGat
Copy link
Copy Markdown
Member

CodeGat commented Aug 1, 2025 •
edited
Loading

Give it another go @aidanheerdegen - I've fixed the bug in dev-v6 (and rebased dev-v6_TEST) in ACCESS-NRI/build-cd@a8d1f82

@github-actions
Copy link
Copy Markdown

github-actions bot commented Aug 6, 2025

🚀 Attempted to deploy access-test Prerelease pr53-2 with commit dc4c005

🖥️ Gadi Deployment ❌

@aidanheerdegen
Copy link
Copy Markdown
Member Author

aidanheerdegen commented Aug 6, 2025

Got an error when I did (effectively) a no-op commit

https://github.com/ACCESS-NRI/ACCESS-TEST/actions/runs/16764395740/job/47466612478?pr=53#step:11:25

  File "/home/runner/work/ACCESS-TEST/ACCESS-TEST/cd/scripts/spack_manifest/injection/prerelease.py", line 22
    >>>>>>> 6c81efe (Dump quoted strings for prerelease projections, updated expected output)
            ^
SyntaxError: invalid decimal literal

Did I need to change something else @CodeGat?

@CodeGat
Copy link
Copy Markdown
Member

CodeGat commented Aug 6, 2025

Looking into this now

@CodeGat CodeGat temporarily deployed to Gadi Prerelease August 6, 2025 02:49 — with GitHub Actions Inactive
@CodeGat
Copy link
Copy Markdown
Member

CodeGat commented Aug 6, 2025 •
edited
Loading

The culprit was a unfixed rebase file conflict in the python file, see ACCESS-NRI/build-cd@bc86b64 @aidanheerdegen 😬

@github-actions
Copy link
Copy Markdown

github-actions bot commented Aug 6, 2025

🚀 Attempted to deploy access-test Prerelease pr53-3 with commit 1a421b4

🖥️ Gadi Deployment ✔️

Usage Instructions

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

  • 2025.06.001 as a Release (when merged).
  • pr53-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/pr53-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/0.22/spack in the access-test-pr53-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 0.22
  • access-nri/spack-packages version main
  • access-nri/spack-config version 2025.07.001

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

@CodeGat
Copy link
Copy Markdown
Member

CodeGat commented Aug 6, 2025 •
edited
Loading

It succeeded, but I found a bug here https://github.com/ACCESS-NRI/ACCESS-TEST/actions/runs/16766276125/job/47471875752?pr=53#step:18:64 - looking for the config/packages.json as if I was on the runner rather than Gadi. Will fix now

@ACCESS-NRI ACCESS-NRI deleted a comment from github-actions bot Aug 6, 2025
@github-actions
Copy link
Copy Markdown

github-actions bot commented Aug 6, 2025

🚀 Attempted to deploy access-test Prerelease pr53-4 with commit 5cdbc6e

🖥️ Gadi Deployment ✔️

Usage Instructions

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

  • 2025.06.001 as a Release (when merged).
  • pr53-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/pr53-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/0.22/spack in the access-test-pr53-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 0.22
  • access-nri/spack-packages version main
  • access-nri/spack-config version 2025.07.001

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

@CodeGat
Copy link
Copy Markdown
Member

CodeGat commented Aug 6, 2025 •
edited
Loading

Bugger, issue with the modulefiles still? https://github.com/ACCESS-NRI/ACCESS-TEST/actions/runs/16768500298/job/47478420175?pr=53#step:16:358

@aidanheerdegen
Copy link
Copy Markdown
Member Author

aidanheerdegen commented Aug 7, 2025

The problem is one of conception (design). To be clear, my conception and my design.

I thought it would be a good idea to put all of the module files under a shared namespace, but the way I'd suggested doing it used the module file name as a directory. So trying to use a path as a file and a directory.

@CodeGat CodeGat temporarily deployed to Gadi Prerelease August 7, 2025 04:07 — with GitHub Actions Inactive
@github-actions
Copy link
Copy Markdown

github-actions bot commented Aug 7, 2025

🚀 Attempted to deploy access-test Prerelease pr53-5 with commit 796f762

🖥️ Gadi Deployment ✔️

Usage Instructions

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

  • 2025.06.001 as a Release (when merged).
  • pr53-5 as a Prerelease (during this PR).

This Prerelease is accessible on Gadi using:

module use /g/data/vk83/prerelease/modules
module load access-test/pr53-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/0.22/spack in the access-test-pr53-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 0.22
  • access-nri/spack-packages version main
  • access-nri/spack-config version 2025.08.000

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

@CodeGat CodeGat temporarily deployed to Gadi Prerelease August 7, 2025 04:25 — with GitHub Actions Inactive
@github-actions
Copy link
Copy Markdown

github-actions bot commented Aug 7, 2025

🚀 Attempted to deploy access-test Prerelease pr53-6 with commit 9161832

🖥️ Gadi Deployment ✔️

Usage Instructions

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

  • 2025.06.001 as a Release (when merged).
  • pr53-6 as a Prerelease (during this PR).

This Prerelease is accessible on Gadi using:

module use /g/data/vk83/prerelease/modules
module load access-test/pr53-6

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-test-pr53-6 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 0.22
  • access-nri/spack-packages version main
  • access-nri/spack-config version 2025.08.000

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

@aidanheerdegen
Copy link
Copy Markdown
Member Author

aidanheerdegen commented Aug 7, 2025

Rejigged the .modulerc and now works. Hooray!

$ module load access-test/pr53-6
Loading access-test/pr53-6
  Loading requirement: access-test/dependencies/pr53-6/openmpi/4.1.5-qg5spmh access-test/dependencies/pr53-6/access-test-component/main-joh6ivi

@CodeGat CodeGat mentioned this pull request Aug 7, 2025
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@CodeGat CodeGat Awaiting requested review from CodeGat CodeGat will be requested when the pull request is marked ready for review CodeGat is a code owner

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

2 participants

@aidanheerdegen @CodeGat