typelevel / typelevel/cats-effect
SIGPIPE during tests on scala-native
Open
Nobody has claimed this yet.
:beetle: bug
- Dominant language
- Scala
- Stars
- 2.2k
- Forks
- 576
- Avg merge
- 2d 11h
- Merged PRs (30d)
- 18
Description
Here: https://github.com/typelevel/cats-effect/actions/runs/19575235491/job/56158173006#step:22:3666
(Linux, x86_64)
[warn] Force close java.lang.RuntimeException: Process /home/runner/work/cats-effect/cats-effect/tests/native/target/scala-3.3.5/cats-effect-tests-test finished with non-zero value 141 (0x8d)
[error] Test runner interrupted by fatal signal 13
Contributor guide
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 with the linked GitHub Actions job, especially the reported test step, and inspect the Scala Native test run at tests/native/target/scala-3.3.5/cats-effect-tests-test. Determine why the test runner receives SIGPIPE (signal 13) and verify that the native tests complete without the non-zero exit value 141.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- scala
- Domain
- operating-systems, testing-qa
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100