Skip to content

Update spack branch spack-stack-dev from spack develop hash a9c879d #1607

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Conversation

climbfuji
Copy link
Collaborator

@climbfuji climbfuji commented Apr 16, 2025

Summary

This PR updates our spack branch spack-stack-dev from spack develop hash a9c879d (last hash before the compilers as dependencies/nodes PR was merged).

Important consequences of this update:

  • Syntax %gcc platform=darwin (or, in general, %compiler variants) must be changed to platform=darwin %gcc
  • core_compilers is not a valid option for TCL modules, remove and update setup-meta-modules extension
  • Bump Python from 3.11.7 to 3.11.11, Openmpi to 5.0.6
  • Remove Ubuntu Intel CI workflow - Intel Classic compilers are no longer supported from this PR onwards
  • Pin glib to 2.78.3 to avoid circular dependency with gobject-introspection
  • Allow installation of deprecated packages (need for py-werkzeug)
  • Update spack imports in spack-stack extension

Also:

  • Update of GitHub runners for unit/util tests (no more Ubuntu 20.04), use newer version of checkout action

NOT DONE IN THIS PR

  • Testing installs on other platforms than the ones listed below
  • Testing builds for JEDI containers

Testing

  • Test installs on @climbfuji's dev systems using Intel LLVM mixed, Intel LLVM, GCC
  • CI
  • Test installs on NRL systems using Intel LLVM mixed, Intel LLVM, GCC

Applications affected

Potentially all

Systems affected

Potentially all (rely on CI testing and fix site configs later during rollout/using spack-stack automation)

Dependencies

Issue(s) addressed

Working towards #1604

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.

Test User and others added 7 commits April 16, 2025 09:31
…ests.yaml: use actions/checkout@v4 and ubuntu-latest instead of ubuntu-20.04
…xt/lib/jcsda-emc/spack-stack/stack/stack_env.py: spack.config.merge_yaml --> spack.schema.merge_yaml
…v/package.py and spack-ext/repos/spack-stack/packages/gmao-swell-env/package.py
…yaml and update spack-ext/lib/jcsda-emc/spack-stack/stack/meta_modules.py accordingly
@climbfuji climbfuji marked this pull request as ready for review April 22, 2025 18:03
@climbfuji climbfuji enabled auto-merge (squash) April 25, 2025 02:51
@climbfuji climbfuji merged commit e70cc5a into JCSDA:develop Apr 25, 2025
8 checks passed
@github-project-automation github-project-automation bot moved this from In Progress to Done in spack-stack-2.0.0 (2025 Q2-Q3) Apr 25, 2025
@climbfuji climbfuji deleted the feature/update_spack_stack_dev_from_spack_a9c879d branch April 25, 2025 13:04
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Development

Successfully merging this pull request may close these issues.

4 participants