Skip to content

[feature/update_to_spack_v1] Update NRL batch install script and NRL site configs; add flag to 'spack stack create env' to promote warnings to errors; updates from develop and release/1.9.0 branches#1798

Merged
climbfuji merged 225 commits intoJCSDA:feature/update_to_spack_v1from
climbfuji:feature/nrl_batch_install_spack_v1
Nov 3, 2025

Conversation

@climbfuji
Copy link
Copy Markdown
Collaborator

@climbfuji climbfuji commented Oct 23, 2025

Description

  1. Add argument --treat-warnings-as-errors for spack stack create env so that warnings for non-existent packages_*.yaml are promoted to errors. The default remains unchanged - they remain warnings.
  2. Update NRL batch install script for spack v1 updates (mostly due to site config updates).
  3. By default, do not create spack compiler modules (not to be confused with meta modules, we definitely do want those by default), use the native compiler modules on HPCs. For user site configs and CI, explicitly add compiler modules to module includelist in configs/sites/**/modules.yaml.
  4. Bring in updates from spack-stack develop (which are updates from the latest release 1.9.3): site configs and wgrib2 variants. All site config updates except NRL sites are from this step.
  5. Remove explicit variants for ewok-env in configs/templates/skylab-dev/spack.yaml and configs/templates/unified-dev/spack.yaml, since they are the default values. This allows us to turn off the ecflow variant in the site configs (c.f. Atlantis).
  6. Add missing export of environment variables from MPI packages in MPI meta modules setup-meta-modules).

Dependencies

Issues addressed

Working towards #1604

Applications affected

None

Systems affected

NRL systems

Testing

  • CI: Note whether the automatic tests (GitHub actions tests that run automatically for every commit) pass or not
    • GitHub actions CI tests pass
    • GitHub actions CI tests do not pass (provide explanation)
    • GitHub actions CI tests skipped (provide explanation if necessary)
  • New tests added: List and describe any new tests added to GitHub actions
    • ...
  • Additional testing: Add information on any additional tests conducted
    • ...

Checklist

  • This PR addresses one issue/problem/enhancement or has a very good reason for not doing so.
  • These changes have been tested on the affected systems and applications.
  • All dependency PRs/issues have been resolved and this PR can be merged.
  • All necessary updates to the documentation on readthedocs are included in this PR deferred
    • For site config updates, check in particular doc/source/PreConfiguredSites.rst and doc/source/MaintainersSection.rst
  • All necessary updates to the spack-stack wiki will be made when this PR is merged deferred

climbfuji added 30 commits July 22, 2025 09:03
…pack-stack to new api version 2 under repos/spack_stack
…pack_stack/spack_repo/spack_stack/packages/neptune_env/package.py, repos/spack_stack/spack_repo/spack_stack/packages/neptune_python_env/package.py
…/spack_repo/spack_stack/packages/neptune_python_env/package.py
@climbfuji climbfuji marked this pull request as ready for review October 31, 2025 14:14
@climbfuji climbfuji enabled auto-merge (squash) November 3, 2025 20:35
@climbfuji climbfuji merged commit 687d84e into JCSDA:feature/update_to_spack_v1 Nov 3, 2025
7 checks passed
@github-project-automation github-project-automation bot moved this from In Progress to Done in spack-stack-2.0.x (2025 Q4) Nov 3, 2025
@climbfuji climbfuji deleted the feature/nrl_batch_install_spack_v1 branch November 3, 2025 21:12
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

NAVY United States Naval Research Lab

Projects

No open projects

Development

Successfully merging this pull request may close these issues.

5 participants