sbt test fail
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 25/100
- Issue type
- Bug
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- scala
- Domain
- build-system, testing-qa
Research direction
Start by reproducing the failure with sbt test and capture the complete output around testfloat_gen and the Pipe closed errors. Trace the test invocation and process-handling code that launches testfloat_gen; done means the relevant tests run without the reported I/O errors.
Written by the indexing model from the issue text.
Description
at scala.sys.process.ProcessImpl$PipeThread.runloop(ProcessImpl.scala:170)
at scala.sys.process.ProcessImpl$PipeSource.run(ProcessImpl.scala:188)
I/O error Pipe closed for process: [testfloat_gen, -rnear_maxMag, -tininessbefore, f16_add]
java.io.IOException: Pipe closed
at java.base/java.io.PipedInputStream.checkStateForReceive(PipedInputStream.java:260)
at java.base/java.io.PipedInputStream.awaitSpace(PipedInputStream.java:268)
at java.base/java.io.PipedInputStream.receive(PipedInputStream.java:231)
at java.base/java.io.PipedOutputStream.write(PipedOutputStream.java:149)
at scala.sys.process.BasicIO$.loop$1(BasicIO.scala:240)
at scala.sys.process.BasicIO$.transferFullyImpl(BasicIO.scala:246)
at scala.sys.process.BasicIO$.transferFully(BasicIO.scala:227)
at scala.sys.process.ProcessImpl$PipeThread.runloop(ProcessImpl.scala:170)
at scala.sys.process.ProcessImpl$PipeSource.run(ProcessImpl.scala:188)
I/O error Pipe closed for process: [testfloat_gen, -rminMag, -tininessbefore, -level2, f16_to_f32]
java.io.IOException: Pipe closed
at java.base/java.io.PipedInputStream.checkStateForReceive(PipedInputStream.java:260)
at java.base/java.io.PipedInputStream.awaitSpace(PipedInputStream.java:268)
at java.base/java.io.PipedInputStream.receive(PipedInputStream.java:231)
- Dominant language
- Scala
- Stars
- 393
- Forks
- 110
- PR merge metrics
- No merged PRs in 30d
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
- 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.
More from ucb-bar/berkeley-hardfloat
-
Difficulty 4/5 3-5 days Newbie friendliness 25/100
ucb-bar/berkeley-hardfloat#86 · 11 comments ·
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
ucb-bar/berkeley-hardfloat#84 · 1 comment ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 25/100
ucb-bar/berkeley-hardfloat#77 · 2 comments ·
-
Difficulty 1/5 Under an hour Newbie friendliness 50/100
-
Difficulty 3/5 1-2 days Newbie friendliness 25/100
ucb-bar/berkeley-hardfloat#59 · 1 comment ·
All issues in ucb-bar/berkeley-hardfloat
Similar issues
-
bug performance priority:medium regression
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
apache/datafusion-comet#6313 ·
Maintainers usually reply within 1 day
-
bug
Difficulty 1/5 Under an hour Newbie friendliness 88/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
com-lihaoyi/mill#7624 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
lichess-org/lila#21845 ·
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 1 day