-
Notifications
You must be signed in to change notification settings - Fork 60
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
2.13: new Scala SHA #1710
2.13: new Scala SHA #1710
Conversation
in local run, |
The culprit PR is scala/scala#10621 It's difficult to discern what the five failures have in common. All five are in test code, but that's probably a red herring — the five projects use four different test frameworks. The error message is different in all five projects. In all five cases, the problem is reproducible outside dbuild. (Locally publishing kind-projector, or changing the dependency to use the 2.13.12 version, is required for two of them.) @lrytz Do you have any theories as to what might be going on here? I eyeballed 10621 but I don't see any obvious leads. I could go digging, but I think the most efficient next step would be for you to have a look and hopefully have a flash of insight. fyi @som-snytt specs2
scala-supertagged
refined
doobie
coulomb
|
Obviously, they're doing something wrong... Maybe "implicits found in package prefix" includes "packages with the word prefix in them":
I can't tell casually what it is testing. I realize you're the only one who knows how dbuild works. Did I try it once? I wouldn't mind publishing a few dependencies locally to try out e.g. coulomb because "it's, um, cool!" Otherwise I will just try something and it will probably just work because it's not testing the thing. @SethTisue forgot to summon[Seth] |
in local testing, 10685 fixed all 5 projects (and is now merged) https://scala-ci.typesafe.com/job/scala-2.13.x-jdk11-integrate-community-build/5213/ queued |
https://scala-ci.typesafe.com/job/scala-2.13.x-jdk11-integrate-community-build/5207/