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

E4S test failures on devel

Open
  • Is something wrong?
#215 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
48/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Active
Tech stack
c
Domain
hpc, testing

Research direction

Start by reproducing the E4S tests on the devel branch with and without Spindle, beginning with adios2, h5bench, lbann, stc, and chapel. Compare the failure output and investigate the chapel timeout; done means all listed tests pass with Spindle in the same environment.

Written by the indexing model from the issue text.

Description

These E4S tests fail with Spindle on devel branch, but pass without Spindle in the same environment:

  • adios2: fails
  • h5bench: fails
  • lbann: fails
  • stc: fails
  • chapel: times out
Dominant language
C
Stars
110
Forks
35
Avg merge
2d 14h
Merged PRs (30d)
12

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

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/Spindle

All issues in llnl/Spindle

Similar issues

More C issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.