Skip to content

Update submodule pointer for repos/builtin (fms oneAPI fp-speculation patch)#2046

Merged
climbfuji merged 1 commit into
JCSDA:release/2.1from
climbfuji:bugfix/rel211_spack_pkgs
Jun 25, 2026
Merged

Update submodule pointer for repos/builtin (fms oneAPI fp-speculation patch)#2046
climbfuji merged 1 commit into
JCSDA:release/2.1from
climbfuji:bugfix/rel211_spack_pkgs

Conversation

@climbfuji

@climbfuji climbfuji commented Jun 24, 2026

Copy link
Copy Markdown
Collaborator

Description

All in the title.

I already retagged the spack-packages submodule as version 2.1.1; will do the same for spack-stack after this PR merges.

Dependencies

None (spack-packages PR already merged).

Issues addressed

None

Applications affected

UFS

Systems affected

None

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 (spack-stack wiki) will be made when this PR is merged

@climbfuji

Copy link
Copy Markdown
Collaborator Author

@rickgrubin-noaa Are you able to review this?

@climbfuji climbfuji merged commit 32d0224 into JCSDA:release/2.1 Jun 25, 2026
6 checks passed
@github-project-automation github-project-automation Bot moved this from In Progress to Done in spack-stack-2.1.x (2026 Q1) Jun 25, 2026
@climbfuji climbfuji deleted the bugfix/rel211_spack_pkgs branch June 25, 2026 15:18
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.

2 participants