Update E4S CI stacks in spack/spack-packages, sync with latest and future, planned releases
Nobody has claimed this yet.
- Dominant language
- Shell
- Stars
- 41
- Forks
- 15
- PR merge metrics
- No merged PRs in 30d
Description
The various E4S stacks at spack/spack-packages should be updated to synchronize with the latest E4S 25.11 release and with future, planned changes.
Planned changes to these Spack Stacks include updating the CI runner images to:
- Use ROCm 7 external stack for the E4S ROCm External Stack
- Use latest OneAPI 2025.3 for the E4S OneAPI stack
Additionally, packages.yaml should be updated to match what is in E4S 25.11 and what is planned for future releases.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start in the stacks directory at spack/spack-packages and inspect packages.yaml, comparing the current definitions with the E4S 25.11 release and the planned changes. Update the E4S stack configurations so the ROCm stack uses the ROCm 7 external stack, the OneAPI stack uses OneAPI 2025.3, and packages.yaml matches the stated releases and plans.
Written by the indexing model from the issue text.
Assessment
- Domain
- build-system, ci-cd, hpc
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100