Failing seed for StreamMergeSuite
Nobody has claimed this yet.
- Dominant language
- Scala
- Stars
- 2.5k
- Forks
- 636
- Avg merge
- 2d 4h
- Merged PRs (30d)
- 7
Description
I came across a failing prop for StreamMergeSuite while trying to debug some platform-specific issues related to CE3.
==> X fs2.StreamMergeSuite.merge - left/right failure - 2 - never-ending flatMap, failure after emit 0.037s munit.FailException: /home/horizon/Desktop/projects/fs2/core/shared/src/test/scala/fs2/StreamMergeSuite.scala:44
43:
44: test("2 - never-ending flatMap, failure after emit") {
45: forAllF { (s1: Stream[Pure, Int]) =>
Failing seed: ZCxsQM1MSYGTOwxjKwtv_cuDjvVN0-hxicvKX_VSr_M=
You can reproduce this failure by adding the following override to your suite:
override val scalaCheckInitialSeed = "ZCxsQM1MSYGTOwxjKwtv_cuDjvVN0-hxicvKX_VSr_M="
Exception raised on property evaluation.
> ARG_0: Stream(..)
> Exception: munit.FailException: /home/horizon/Desktop/projects/fs2/core/shared/src/test/scala/fs2/StreamMergeSuite.scala:50 Expected an exception of type fs2.Err but got a result: ()
49: .drain
50: .assertThrows[Err]
51: }
Another failing seed for the same test hP-8mu5fDOvtStGfsFrK5SSr1mQDrJnJya3xaUwSwQC=.
FWIW this was seen on openjdk8 on an ubuntu VM running inside vmware fusion for mac.
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 core/shared/src/test/scala/fs2/StreamMergeSuite.scala, especially the test at lines 44-50. Reproduce it by overriding scalaCheckInitialSeed with one of the reported seeds, then inspect why the never-ending flatMap case returns successfully instead of raising fs2.Err; done means the property passes for the reported seeds.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- scala
- Domain
- stream-processing, testing
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100