Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Move away from flux wrapper on TOSS4Cray

Open
#1,671 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 2 days

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
42/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Active
Tech stack
cmake
Domain
build-system

Research direction

Start with the TOSS4Cray Spack configuration linked in the issue, especially scripts/spack/configs/toss_4_x86_64_ib_cray/spack.yaml, and compare its process-manager settings with the referenced cached_cmake.py logic and cray-mpich package. The issue suggests solving this with a local package override, but does not specify its implementation or tests. Done means TOSS4Cray no longer relies on the flux wrapper; confirm the resulting configuration builds and uses the intended process manager.

Written by the indexing model from the issue text.

Description

I'm beginning to remember issues here. The cray-mpich package doesn't have a variant to control the process manager... like here:

https://github.com/spack/spack-packages/blob/3b7fdffc24511b067b65540e0e9b3c89d07f8a7f/repos/spack_repo/builtin/packages/mvapich2/package.py#L82-L90

Normally we would swap slurm to flux here:

https://github.com/llnl/smith/blob/84a50319b297c994ab2a9a54de0ac56f16842beb/scripts/spack/configs/toss_4_x86_64_ib_cray/spack.yaml#L60-L61

which would flip this logic:

https://github.com/spack/spack-packages/blob/3b7fdffc24511b067b65540e0e9b3c89d07f8a7f/repos/spack_repo/builtin/build_systems/cached_cmake.py#L200-L224

I'll see if I can get Spack to engage this more than last time but we could solve this for ourselves by overriding the package like we are doing now for us.

Originally posted by @white238 in https://github.com/llnl/smith/pull/1669#discussion_r4190394418

Dominant language
C++
Stars
246
Forks
37
Avg merge
2d 14h
Merged PRs (30d)
10

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from llnl/smith

All issues in llnl/smith

Similar issues

More C++ issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.