Skip to content

Move spack core commit forward#1318

Open
scheibelp wants to merge 4 commits into
developfrom
update-spack
Open

Move spack core commit forward#1318
scheibelp wants to merge 4 commits into
developfrom
update-spack

Conversation

@scheibelp

@scheibelp scheibelp commented Apr 20, 2026

Copy link
Copy Markdown
Collaborator

This moves the spack commit forward from Dec. 1 2025 to Mar. 27 2026 May 5 2026, in preparation for new hip-lang functionality (that will come from spack-packages, although is not available there yet, this commit in spack-core will be sufficient).

@rfhaque rfhaque mentioned this pull request May 2, 2026
1 task
@pearce8 pearce8 added this to the May 2026 milestone May 4, 2026
@michaelmckinsey1

michaelmckinsey1 commented May 8, 2026

Copy link
Copy Markdown
Collaborator

https://lc.llnl.gov/gitlab/benchpark/benchpark/-/pipelines/702231

I've manually checked this pipeline and don't see any new failures

@codecov-commenter

Copy link
Copy Markdown

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 64.26%. Comparing base (7db9c96) to head (74dd198).
⚠️ Report is 1 commits behind head on develop.

Additional details and impacted files
@@           Coverage Diff            @@
##           develop    #1318   +/-   ##
========================================
  Coverage    64.26%   64.26%           
========================================
  Files           49       49           
  Lines         3811     3811           
  Branches       338      338           
========================================
  Hits          2449     2449           
  Misses        1343     1343           
  Partials        19       19           
🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

@scheibelp

scheibelp commented May 8, 2026

Copy link
Copy Markdown
Collaborator Author

(this is running into some issues with spack/spack#51957 - I will try to sort this out by end of Monday)

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.

4 participants