Fatal exceptions hang the runner
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 35/100
Research direction
Start by running the supplied Scala reproducer or the linked repro project and confirm that a fatal exception hangs the runner. Then inspect the runner's fatal-exception handling and related issue #503; done means the suite terminates with the exception instead of hanging, consistently with the reported munit and scalatest behavior.
Written by the indexing model from the issue text.
Description
This issue was copied over from: https://github.com/disneystreaming/weaver-test/issues/651
It was opened by: kubukoz
Using 0.8.3, when you run this suite (or anything else that produces an exception of the "fatal" sort), it hangs the runner.
import weaver._
import cats.effect.IO
object DemoTestWeaver extends SimpleIOSuite {
pureTest("demo") {
throw new NoClassDefFoundError("fake exception")
}
}
This is inconsistent with munit and scalatest's behavior, and hopefully it's something that can be fixed on weaver's side.
Related: #503
Repro project: https://github.com/kubukoz/demos/tree/sbt-weaver-hang
- Dominant language
- Scala
- Stars
- 85
- Forks
- 15
- PR merge metrics
- No merged PRs in 30d
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.
More from typelevel/weaver-test
-
Difficulty 3/5 1-2 days Newbie friendliness 65/100
typelevel/weaver-test#302 · 3 comments ·
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
typelevel/weaver-test#262 · 2 comments ·
-
Difficulty 5/5 Over a week Newbie friendliness 35/100
typelevel/weaver-test#233 · 3 comments · 2 reactions ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 52/100
typelevel/weaver-test#201 ·
-
Difficulty 4/5 3-5 days Newbie friendliness 25/100
typelevel/weaver-test#180 ·
All issues in typelevel/weaver-test
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
ergoplatform/ergodocs#614 ·
-
area:ci enhancement requires-triage
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
apache/datafusion-comet#6078 ·
-
Difficulty 1/5 Under an hour Newbie friendliness 90/100
-
[VL] madvise(WILLNEED) call fails in MmapFileStream because of wrong calculation of fetching length Openbug triage
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
chipsalliance/rocket-chip#3831 ·