Skip to content
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

NoDenotation error with scala 3.3.0 #511

Open
frozenwizard opened this issue Sep 5, 2023 · 4 comments
Open

NoDenotation error with scala 3.3.0 #511

frozenwizard opened this issue Sep 5, 2023 · 4 comments

Comments

@frozenwizard
Copy link

I have a project that was running fine under 3.2.1 with coverage. I upgraded to scala 3.3.0 and also sbt-tpolecat and scoverage to the latest versions. Now when I run coverage on tests and integration tests they fail during compilation with an error I don't understand.


java.lang.AssertionError: NoDenotation.owner while running MegaPhase{crossVersionChecks, protectedAccessors, extmethods, uncacheGivenAliases, elimByName, hoistSuperArgs, forwardDepChecks, specializeApplyMethods, tryCatchPatterns, patternMatcher} on /builds/Myfile.scala
[info] exception occurred while compiling /builds/<my project files here>
java.lang.AssertionError: NoDenotation.owner while compiling <insert my scala files here>
[error] ## Exception when compiling 13 sources to /builds/my-project/target/scala-3.3.0/classes
[error] java.lang.AssertionError: NoDenotation.owner
[error] dotty.tools.dotc.core.SymDenotations$NoDenotation$.owner(SymDenotations.scala:2576)
[error] dotty.tools.dotc.transform.HoistSuperArgs$Hoister.hoistSuperArgsFromCall(HoistSuperArgs.scala:185)

When running test/itests on their own there is no issue, only when I add in the coverage to "sbt coverage test" does it fail. This error seems to be a compiler error?

@ckipp01
Copy link
Member

ckipp01 commented Sep 18, 2023

Hey @frozenwizard, do you have a code sample that we can reproduce this with?

@frozenwizard
Copy link
Author

I can possibly work one out in a few days.

@ckipp01
Copy link
Member

ckipp01 commented Sep 19, 2023

I can possibly work one out in a few days.

Perfect, thanks. That way we can verify where the issue actually is and probably report it upstream since it looks to be stemming from there.

@joca0612
Copy link

joca0612 commented Nov 3, 2023

I encountered the same error. Do you have any guidance on how I can figure out the source of the issue to reproduce it? My project is really large and the stacktrace does not help (it is similar to the original poster). I tried running coverage using -Ycheck:all but still no clue. For reference, it seems like this was considered solved on the lang side

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants