Skip to content

Testing upstream ISSM update & new spack-variant#26

Draft
lawrenceabird wants to merge 18 commits intomainfrom
lb/upstream-latest
Draft

Testing upstream ISSM update & new spack-variant#26
lawrenceabird wants to merge 18 commits intomainfrom
lb/upstream-latest

Conversation

@lawrenceabird
Copy link
Copy Markdown
Collaborator

@lawrenceabird lawrenceabird commented Oct 16, 2025

This draft PR tests a new build of ACCESS-ISSM based on an updated ISSM code base. It also integrates updates to the ISSM spack-package that have been implemented here.


🚀 The latest prerelease access-issm/pr26-3 at 45ffe58 is here: #26 (comment) 🚀

- Point to specific commit for latest ISSM version.
- Add py-tools to include Python code.
@github-actions
Copy link
Copy Markdown

🚀 Attempted to deploy access-issm Prerelease pr26-1 with commit 6252137

🖥️ Gadi Deployment ✔️

Usage Instructions

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

  • 2025.03.0 as a Release (when merged).
  • pr26-1 as a Prerelease (during this PR).

This Prerelease is accessible on Gadi using:

module use /g/data/vk83/prerelease/modules
module load access-issm/pr26-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-issm-pr26-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.

Update spack-packages to new version that includes +py-tools variant, and sets $ISSM_DIR $PYTHONPATH environment variables.
Revert ISSM code to existing release state to test (A) ONLY Py-tool variant; (B) Correct toolkit generation on gadi
@github-actions
Copy link
Copy Markdown

🚀 Attempted to deploy access-issm Prerelease pr26-2 with commit 054a871

🖥️ Gadi Deployment ✔️

Usage Instructions

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

  • 2025.03.0 as a Release (when merged).
  • pr26-2 as a Prerelease (during this PR).

This Prerelease is accessible on Gadi using:

module use /g/data/vk83/prerelease/modules
module load access-issm/pr26-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/0.22/spack in the access-issm-pr26-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:

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

The ISSM package.py specifies that petsc should only be used when ~ad is specified. ad default = False, but perhaps it needs to be explicitly specified.
@github-actions
Copy link
Copy Markdown

🚀 Attempted to deploy access-issm Prerelease pr26-3 with commit f34034a

🖥️ Gadi Deployment ✔️

Usage Instructions

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

  • 2025.03.0 as a Release (when merged).
  • pr26-3 as a Prerelease (during this PR).

This Prerelease is accessible on Gadi using:

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

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

Try forcing the specification of +openmp to overcome openmpi dependency issue.
@github-actions
Copy link
Copy Markdown

🚀 Attempted to deploy access-issm Prerelease pr26-4 with commit d906b63

🖥️ Gadi Deployment ✔️

Usage Instructions

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

  • 2025.03.0 as a Release (when merged).
  • pr26-4 as a Prerelease (during this PR).

This Prerelease is accessible on Gadi using:

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

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

Following tests of spack-package updates, now try rebuilding with newer ISSM code base again.
@github-actions
Copy link
Copy Markdown

🚀 Attempted to deploy access-issm Prerelease pr26-5 with commit ad650b7

🖥️ Gadi Deployment ✔️

Usage Instructions

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

  • 2025.03.0 as a Release (when merged).
  • pr26-5 as a Prerelease (during this PR).

This Prerelease is accessible on Gadi using:

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

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

Remove ~ad and +openmp to confirm that this is responsible for Petsc build issue.
@github-actions
Copy link
Copy Markdown

🚀 Attempted to deploy access-issm Prerelease pr26-6 with commit 31fe38a

🖥️ Gadi Deployment ✔️

Usage Instructions

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

  • 2025.03.0 as a Release (when merged).
  • pr26-6 as a Prerelease (during this PR).

This Prerelease is accessible on Gadi using:

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

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

Add ~ad again to test if this build with Petsc
@github-actions
Copy link
Copy Markdown

🚀 Attempted to deploy access-issm Prerelease pr26-7 with commit 0814150

🖥️ Gadi Deployment ✔️

Usage Instructions

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

  • 2025.03.0 as a Release (when merged).
  • pr26-7 as a Prerelease (during this PR).

This Prerelease is accessible on Gadi using:

module use /g/data/vk83/prerelease/modules
module load access-issm/pr26-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-issm-pr26-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.

@github-actions
Copy link
Copy Markdown

🚀 Attempted to deploy access-issm Prerelease pr26-8 with commit 8f6e205

🖥️ Gadi Deployment ✔️

Usage Instructions

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

  • 2025.03.0 as a Release (when merged).
  • pr26-8 as a Prerelease (during this PR).

This Prerelease is accessible on Gadi using:

module use /g/data/vk83/prerelease/modules
module load access-issm/pr26-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-issm-pr26-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.

~ad should be default. Which means it should build with Petsc
@github-actions
Copy link
Copy Markdown

🚀 Attempted to deploy access-issm Prerelease pr26-9 with commit 9993894

🖥️ Gadi Deployment ✔️

Usage Instructions

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

  • 2025.03.0 as a Release (when merged).
  • pr26-9 as a Prerelease (during this PR).

This Prerelease is accessible on Gadi using:

module use /g/data/vk83/prerelease/modules
module load access-issm/pr26-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-issm-pr26-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
Copy link
Copy Markdown

🚀 Attempted to deploy access-issm Prerelease pr26-10 with commit 9c41dd9

🖥️ Gadi Deployment ❌

@github-actions
Copy link
Copy Markdown

🚀 Attempted to deploy access-issm Prerelease pr26-11 with commit 9c41dd9

🖥️ Gadi Deployment ❌

@github-actions
Copy link
Copy Markdown

🚀 Attempted to deploy access-issm Prerelease pr26-12 with commit 9c41dd9

🖥️ Gadi Deployment ❌

@github-actions
Copy link
Copy Markdown

🚀 Attempted to deploy access-issm Prerelease pr26-13 with commit 9c41dd9

🖥️ Gadi Deployment ✔️

Usage Instructions

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

  • 2025.03.0 as a Release (when merged).
  • pr26-13 as a Prerelease (during this PR).

This Prerelease is accessible on Gadi using:

module use /g/data/vk83/prerelease/modules
module load access-issm/pr26-13

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-issm-pr26-13 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
Copy link
Copy Markdown

🚀 Attempted to deploy access-issm Prerelease pr26-14 with commit 9c41dd9

🖥️ Gadi Deployment ✔️

Usage Instructions

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

  • 2025.03.0 as a Release (when merged).
  • pr26-14 as a Prerelease (during this PR).

This Prerelease is accessible on Gadi using:

module use /g/data/vk83/prerelease/modules
module load access-issm/pr26-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/0.22/spack in the access-issm-pr26-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.

@github-actions
Copy link
Copy Markdown

🚀 Attempted to deploy access-issm Prerelease pr26-15 with commit d0b53f6

🖥️ Gadi Deployment ✔️

Usage Instructions

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

  • 2025.03.0 as a Release (when merged).
  • pr26-15 as a Prerelease (during this PR).

This Prerelease is accessible on Gadi using:

module use /g/data/vk83/prerelease/modules
module load access-issm/pr26-15

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-issm-pr26-15 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.

Testing latest ISSM build (7f75a90562fae6834a33bdc6276eaa5dc2cbcf66) without AD
@github-actions
Copy link
Copy Markdown

🚀 Attempted to deploy access-issm Prerelease pr26-16 with commit 0394656

🖥️ Gadi Deployment ✔️

Usage Instructions

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

  • 2025.03.0 as a Release (when merged).
  • pr26-16 as a Prerelease (during this PR).

This Prerelease is accessible on Gadi using:

module use /g/data/vk83/prerelease/modules
module load access-issm/pr26-16

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-issm-pr26-16 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
Copy link
Copy Markdown

🚀 Attempted to deploy access-issm Prerelease pr26-17 with commit 914e6b3

🖥️ Gadi Deployment ✔️

Usage Instructions

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

  • 2025.03.0 as a Release (when merged).
  • pr26-17 as a Prerelease (during this PR).

This Prerelease is accessible on Gadi using:

module use /g/data/vk83/prerelease/modules
module load access-issm/pr26-17

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-issm-pr26-17 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.

@lawrenceabird
Copy link
Copy Markdown
Collaborator Author

Build succeeded, but there is an error at module load:

load access-issm/pr26-17[lb9857@gadi-login-07 lb9857]$ module load access-issm/pr26-17
Loading access-issm/dependencies/pr26-17/issm/7f75a90562fae6834a33bdc6276eaa5dc2cbcf66-vd7km2e
  ERROR: Unable to locate a modulefile for 'access-issm/dependencies/pr26-17/openmpi/4.1.7-3enketu'
  ERROR: Requirement access-issm/dependencies/pr26-17/openmpi/4.1.7-3enketu is not loaded

Loading access-issm/pr26-17
  ERROR: Load of requirement access-issm/dependencies/pr26-17/openmpi/4.1.7-3enketu failed
  ERROR: Load of requirement access-issm/dependencies/pr26-17/issm/7f75a90562fae6834a33bdc6276eaa5dc2cbcf66-vd7km2e failed

Trying a redeploy with no changes.

@github-actions
Copy link
Copy Markdown

🚀 Attempted to deploy access-issm Prerelease pr26-18 with commit 914e6b3

🖥️ Gadi Deployment ✔️

Usage Instructions

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

  • 2025.03.0 as a Release (when merged).
  • pr26-18 as a Prerelease (during this PR).

This Prerelease is accessible on Gadi using:

module use /g/data/vk83/prerelease/modules
module load access-issm/pr26-18

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-issm-pr26-18 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.

@lawrenceabird
Copy link
Copy Markdown
Collaborator Author

lawrenceabird commented Oct 28, 2025

Build successfully; module load successful, and toolkits file looks correct. Model run successful, but with various warnings in *.outlog

[gadi-cpu-clx-1621:23:2539892 - context.c:307][2025-10-28 15:03:09] ERROR failed to initialize sharp
Failed to open log file (stdout)[gadi-cpu-clx-1621:15:2539885 - context.c:307][2025-10-28 15:03:09] ERROR failed to initialize sharp
Failed to open log file (stdout)[gadi-cpu-clx-1621:5:2539876 - context.c:307][2025-10-28 15:03:09] ERROR failed to initialize sharp
Failed to open log file (stdout)[gadi-cpu-clx-1621:2:2539873 - context.c:307][2025-10-28 15:03:09] ERROR failed to initialize sharp
Failed to open log file (stdout)[gadi-cpu-clx-1621:0:2539871 - context.c:307][2025-10-28 15:03:09] ERROR failed to initialize sharp
Failed to open log file (stdout)Failed to open log file (stdout)[gadi-cpu-clx-1621:17:2539889 - context.c:307][2025-10-28 15:03:09] ERROR failed to initialize sharp
[gadi-cpu-clx-1621:4:2539878 - context.c:307][2025-10-28 15:03:09] ERROR failed to initialize sharp

I think this is related to openMP flags. In the build log associated with the latest build (pr26-18), the petsc variants look like:

^petsc@3.21.1%gcc@13.2.0~X~batch~cgns~complex~cuda~debug+double~examples~exodusii~fftw+fortran~giflib+hdf5~hpddm~hwloc+hypre~int64~jpeg~knl~kokkos~libpng~libyaml~memkind+metis~mkl-pardiso~mmg~moab~mpfr+mpi+mumps~openmp~p4est~parmmg~ptscotch~random123~rocm~saws+scalapack+shared~strumpack~suite-sparse+superlu-dist~sycl~tetgen~trilinos~valgrind~zoltan build_system=generic clanguage=C memalign=none arch=linux-rocky8-x86_64

This potentially suggests that openmp is being disabled by default with petsc+mumps options.

Next steps:

  1. Test build with +ad to ensure that petsc is dropped.
  2. Update spack-packages to add openmp flag to mumps (And add necessary additional conditions: depends_on("petsc~examples+metis+mumps+openmp+scalapack")

@github-actions
Copy link
Copy Markdown

🚀 Attempted to deploy access-issm Prerelease pr26-19 with commit e87dce8

🖥️ Gadi Deployment ✔️

Usage Instructions

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

  • 2025.03.0 as a Release (when merged).
  • pr26-19 as a Prerelease (during this PR).

This Prerelease is accessible on Gadi using:

module use /g/data/vk83/prerelease/modules
module load access-issm/pr26-19

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-issm-pr26-19 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.

@lawrenceabird
Copy link
Copy Markdown
Collaborator Author

AD Model launched, but failed due to an ISSM error. Next tests:

  1. Rebuild ~ad (default) variant with +openmp variant passed to petsc. Does this fix the log file errors in the *.outlog file?
  2. Rebuild +ad variant with comparable ISSM version that Felicity has on her local machine 4a8c078eefe06f23665322e153b35f8594b4e626 to see if execution completes.

@github-actions
Copy link
Copy Markdown

🚀 Attempted to deploy access-issm Prerelease pr26-19 with commit e063619

🖥️ Gadi Deployment ✔️

Usage Instructions

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

  • 2025.03.0 as a Release (when merged).
  • pr26-19 as a Prerelease (during this PR).

This Prerelease is accessible on Gadi using:

module use /g/data/vk83/prerelease/modules
module load access-issm/pr26-19

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-issm-pr26-19 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.

@lawrenceabird
Copy link
Copy Markdown
Collaborator Author

Model build and module load successful. But, Petsc not found in toolkits. Redeploy to ensure it wasn't just a build error.

@lawrenceabird
Copy link
Copy Markdown
Collaborator Author

!redeploy

@github-actions
Copy link
Copy Markdown

🚀 Attempted to deploy access-issm Prerelease pr26-2 with commit e063619

🖥️ Gadi Deployment ✔️

Usage Instructions

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

  • 2025.03.0 as a Release (when merged).
  • pr26-2 as a Prerelease (during this PR).

This Prerelease is accessible on Gadi using:

module use /g/data/vk83/prerelease/modules
module load access-issm/pr26-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/0.22/spack in the access-issm-pr26-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:

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

@lawrenceabird
Copy link
Copy Markdown
Collaborator Author

Same issue. Petsc not found in toolkits. Adding +openmp to depends_on(petsc...) appears to cause this issue. Try now to add +openmp variant to the mumps variant of petsc only. See commit 45ffe58.

@github-actions
Copy link
Copy Markdown

🚀 Attempted to deploy access-issm Prerelease pr26-3 with commit 45ffe58

🖥️ Gadi Deployment ❌

@lawrenceabird
Copy link
Copy Markdown
Collaborator Author

!redeploy

@github-actions
Copy link
Copy Markdown

🚀 Attempted to deploy access-issm Prerelease pr26-3 with commit 45ffe58

🖥️ Gadi Deployment ✔️

Usage Instructions

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

  • 2025.03.0 as a Release (when merged).
  • pr26-3 as a Prerelease (during this PR).

This Prerelease is accessible on Gadi using:

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

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

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