-
Notifications
You must be signed in to change notification settings - Fork 91
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Broken Scala Native tests on v1.0.0-M9 #695
Comments
More details in this CE issue. I'm operating under the assumption that this is a CE bug, but I'm not sure yet. |
I was able to reproduce without CE. //> using dep org.scalameta::munit::1.0.0-M9
//> using nativeVersion 0.4.15
import scala.concurrent.duration.*
import scala.concurrent.*
class MySuite extends munit.FunSuite:
override implicit def munitExecutionContext = ExecutionContext.global
test("boo"):
val p = Promise[Unit]()
ExecutionContext.global.execute { () =>
Thread.sleep(1000)
p.success(())
}
p.future |
One tiny step further, we can drop the //> using dep org.scalameta::munit::1.0.0-M9
//> using nativeVersion 0.4.15
import scala.concurrent.duration.*
import scala.concurrent.*
class MySuite extends munit.FunSuite:
override implicit def munitExecutionContext = ExecutionContext.global
test("boo"):
val p = Promise[Unit]()
ExecutionContext.global.execute { () => p.success(()) }
p.future
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The latest milestone release (v1.0.0-M9) appears to break tests on Scala Native.
The likely culprit is some complication with #693 interacting with cats-effect.
Related links:
munit-cats-effect failing build on M9
Invalid opcode 4 on munit async tests scala-native/scala-native#3464
Edit: If downstream users see an error like:
This is actually caused by not being on the latest Scala Native 0.4.15
The text was updated successfully, but these errors were encountered: