typelevel / typelevel/cats-effect
IOAppSuite failure on JDK 25
Open
Nobody has claimed this yet.
- Dominant language
- Scala
- Stars
- 2.2k
- Forks
- 576
- Avg merge
- 2d 11h
- Merged PRs (30d)
- 18
Description
as seen in the Scala 2.13 community build at https://scala-ci.typesafe.com/job/scala-2.13.x-jdk25-integrate-community-build/9/artifact/logs/cats-effect-build.log :
[cats-effect] [error] ==> X cats.effect.IOAppSuite.support main thread evaluation 0.422s munit.ComparisonFailException: ioapp-tests/src/test/scala/IOAppSuite.scala:361
[cats-effect] [error] 360: val h = platform("EvalOnMainThread", List.empty)
[cats-effect] [error] 361: assertEquals(h.awaitStatus(), 0)
[cats-effect] [error] 362: }
[cats-effect] [error] values are not the same
[cats-effect] [error] => Obtained
[cats-effect] [error] 1
[cats-effect] [error] => Diff (- expected, + obtained)
[cats-effect] [error] -0
[cats-effect] [error] +1
[cats-effect] [error] at munit.FunSuite.assertEquals(FunSuite.scala:13)
[cats-effect] [error] at cats.effect.IOAppSuite.$anonfun$new$91(IOAppSuite.scala:361)
I assume it's easily reproducible, but if not, lmk
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 by reproducing the Scala 2.13 community-build failure on JDK 25 and read ioapp-tests/src/test/scala/IOAppSuite.scala around line 361. Investigate why the EvalOnMainThread case reports status 1 instead of 0; done means the test passes on the affected JDK version.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- scala
- Domain
- testing-qa
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100