-
Notifications
You must be signed in to change notification settings - Fork 1.1k
Tests with explicit nulls are broken on main branch #22988
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
Comments
Have you found a way to reproduce it in sbt? I haven't yet. I would guess it's probably some interaction between CC, which wraps types in Tasty inside But first I need to be able to reproduce it outside of the CI. |
But I see that this is only one of many errors. We should revert #22473, figure out how to run these tests outside of CI, and then debug it offline before merging it again. |
The following sbt commands reproduce this:
|
For the specific test mentioned above, it's:
|
It seems the problems are unrelated to CC. The same errors come up with
So just having the standard library coming from Tasty is enough to cause the errors. |
It seems the CI is failing on main branch because of the PR #22473.
The errors only happen in "Test Suite with the CC Standard Library". Maybe related to cc library compiled in explicit nulls?
One of the failed tests is a debug test introduced by #22597, but the error message does not give much information...
cc @HarrisL2 @olhotak
The text was updated successfully, but these errors were encountered: