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

[javac] some differences ecj <-> javac regarding 'recent' features #2959

Open
stephan-herrmann opened this issue Sep 15, 2024 · 0 comments
Open
Assignees
Labels
test Work on unit tests, no change of productive code

Comments

@stephan-herrmann
Copy link
Contributor

While taking stock of run.javac test results regarding Java 23 I observed the following differences which might be within reach for resolution:

  • PrimitiveInPatternsTestSH
  • MarkdownCommentTest:
    • 1 error, javac not complaining about unresolvable @see reference
  • ModuleCompilationTests
    • 4 errors
  • PatternMatching16Test -- is this a structural problem?
    • 83 failures, obviously not suitable for running back-to-back with javac23
    • 67 errors vs javac16
  • RecordPatternTest 3 errors, javac-generated code throws ArithmeticException instead of expected MatchException (see comments in tests):
    • testGH1977_instance_field()
    • testGH1977_static_field()
    • testIssue1985_2()
  • SwitchExpressionsYieldTest
    • currently 175 failures, many of which due to ill-configured javac invocation
    • remaining: 17 failures
  • SwitchPatternTest: 5 errors (some related to wrongly configured --enable-preview, others not yet analysed)
  • SwitchPatternTest21: 2 errors
    * testInternalDomination_this() (ecj no error, javac 2 errors)
    * testNaming() // javac jdk21 allows components to be named, but they can't be referenced
@stephan-herrmann stephan-herrmann self-assigned this Sep 15, 2024
stephan-herrmann added a commit to stephan-herrmann/eclipse.jdt.core that referenced this issue Sep 15, 2024
+ fix arguments of javac invocations
+ remove a forgotten test filter

relates to eclipse-jdt#2959
@stephan-herrmann stephan-herrmann added the test Work on unit tests, no change of productive code label Sep 15, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
test Work on unit tests, no change of productive code
Projects
None yet
Development

No branches or pull requests

1 participant