Revive tests for sbt-bridge #16659
Merged
Revive tests for sbt-bridge #16659
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
prolativ
force-pushed
the
sbt-bridge-tests
branch
from
2a0e3fa to
e567791
Compare
prolativ
force-pushed
the
sbt-bridge-tests
branch
from
e567791 to
9ad1fdb
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
reuseCompilerInstanceoption was removed, as now, when we trigger compilation directly via the bridge, a new instance of the compiler is created for each group of sources. However, it looks like this previously available distinction was never used effectivelyobjectStandardNamesin expected test results were removed because now the fact that all objects extendSerializableis not visible in the typer but added during bytecode generation