-
Notifications
You must be signed in to change notification settings - Fork 126
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
Scala 3.0.0 #177
Scala 3.0.0 #177
Conversation
There is a connection link failure that may be a timing issue. Re-run maybe? |
Looks like it. Re-running... |
Sorry, I committed a metals file. Deleted. |
Hm, still failing with mysql test. I'll take a look over this week. |
Turns out it's related to this testcontainers/testcontainers-java#4058 |
@tpolecat I merged the fix for mysql spec to master. Would you mind merging it to your branch? |
Ok I rebased. |
@tpolecat thanks! now it's failing with:
Do you think it's related to your change or it's new flakiness? Anyways, I can try to dig into it in next few days. |
I saw this exception locally but it didn't happen initially in CI so I thought it was some local quirk. This should only be possible if we compile against one version and run against another (unless they're using reflection somewhere). The sbt eviction report shows nothing suspicious. |
Went ahead and upgraded to 3.0.0 |
Hm, still the same error. I'm still trying to figure out why it's failing. |
Anything we can do to help? |
Hi @milessabin, sorry, it has been a busy week and I haven't had a chance to take a look. |
I'm going to dig into this today and see what I can figure out. |
I narrowed it down to what I think is a compiler bug, here scala/scala3#12586. I will write a Java stub to work around it for now. |
This updates testcontainers to Scala
3.0.0-RC33.0.0.