Community
Participate
Working Groups
Follow up of review in bug 535918 comment 12 : Trying to run affected tests back-to-back with javac it seems that our tests are not ready for this exercise? I got: java.lang.RuntimeException: unknown raw javac version: 11 at org.eclipse.jdt.core.tests.compiler.regression.AbstractRegressionTest$JavacCompiler.minorFromRawVersion(AbstractRegressionTest.java:390) Looks like this can be easily fixed by a new stanza in org.eclipse.jdt.core.tests.compiler.regression.AbstractRegressionTest.JavacCompiler.JavacCompiler(String, String) Do we have an open bug for that kind of adjustments in tests? FYI, I'm using these additional VM args: -ea -Drun.javac=enabled -Djdk.root=/home/java/jdk-11 -Dcompliance=11 Are we ready to rededicate [1] to Java 11? Or should I create an additional Job? [1] https://ci.eclipse.org/jdt/job/eclipse.jdt.core-run.javac-10/
New Gerrit change created: https://git.eclipse.org/r/129399
Gerrit change https://git.eclipse.org/r/129399 was merged to [BETA_JAVA11]. Commit: http://git.eclipse.org/c/jdt/eclipse.jdt.core.git/commit/?id=ecaf2e1e8a7dfe076050a2394831418f17c60675
Sorry, but ParserTest is not yet ready to run on 11, see https://ci.eclipse.org/jdt/job/eclipse.jdt.core-run.javac-11/3/testReport/org.eclipse.jdt.core.tests.compiler.parser/ParserTest/test001___11/ More of the same seems to be needed. Additionally, failures in JEP181NestTest seem to indicate we don't run our test programs on JRE 11, see e.g. https://ci.eclipse.org/jdt/job/eclipse.jdt.core-run.javac-11/3/testReport/org.eclipse.jdt.core.tests.compiler.regression/JEP181NestTest/testBug535918_001a___11/ Or, the used jre would not be able to handle access among nest mates?? Tests claim to be using this version: openjdk version "11-ea" 2018-09-25 OpenJDK Runtime Environment 18.9 (build 11-ea+23) OpenJDK 64-Bit Server VM 18.9 (build 11-ea+23, mixed mode) (interesting date "2018-09-25") According to build logs, this is the command line by which our tests are executed: /opt/public/common/java/oracle/jdk-11_x64-latest/bin/java, -Dosgi.noShutdown=false, -Dosgi.os=linux, -Dosgi.ws=gtk, -Dosgi.arch=x86_64, --add-modules, ALL-SYSTEM, -Drun.javac=enabled, -Djdk.root=/shared/common/java/openjdk/jdk-11_x64-latest/, -Dcompliance=11, -Dosgi.clean=true, -jar, /jobs/genie.jdt/eclipse.jdt.core-run.javac-11/workspace/.repository/p2/osgi/bundle/org.eclipse.equinox.launcher/1.5.100.v20180827-1352/org.eclipse.equinox.launcher-1.5.100.v20180827-1352.jar, -data, /jobs/genie.jdt/eclipse.jdt.core-run.javac-11/workspace/org.eclipse.jdt.core.tests.compiler/target/work/data, -install, /jobs/genie.jdt/eclipse.jdt.core-run.javac-11/workspace/org.eclipse.jdt.core.tests.compiler/target/work, -configuration, /jobs/genie.jdt/eclipse.jdt.core-run.javac-11/workspace/org.eclipse.jdt.core.tests.compiler/target/work/configuration, -application, org.eclipse.tycho.surefire.osgibooter.headlesstest, -testproperties, /jobs/genie.jdt/eclipse.jdt.core-run.javac-11/workspace/org.eclipse.jdt.core.tests.compiler/target/surefire.properties Running just JEP181NestTest locally from Eclipse (with run.javac=enabled) is green. Any ideas?
@Stephan: I see this error with JEP181Test with ea18 where the nestmates are not supported but with ea+23 this error goes away as this version supports nestmate. I am running the tests with 28 now with all green on a local run, for ParserTest and JEP181Test as green. Can you please try with build 28?
(In reply to Manoj Palat from comment #4) > @Stephan: I see this error with JEP181Test with ea18 where the nestmates > are not supported but with ea+23 this error goes away as this version > supports nestmate. I am running the tests with 28 now with all green on a > local run, for ParserTest and JEP181Test as green. Can you please try with > build 28? Locally, I see the same, but jenkins disagrees. Filed bug 539122 for what I guess to be the cause of confusion.
Created attachment 275839 [details] Test results While jenkins cannot yet provide the results, PFA the results from running tests.compiler.regression locally against javac11. Please see that against javac10 we currently have approx. 230 failures [1], whereas the attached result lists 328 failures! Some differences might be due to fixes in master which are not yet in BETA_JAVA11. At least JEP181NestTest is listed in green :) [1] https://ci.eclipse.org/jdt/job/eclipse.jdt.core-run.javac-10/43/testReport/
We do have our first results from our Jenkins job testing back-to-back with javac11: https://hudson.eclipse.org/jdt/job/eclipse.jdt.core-run.javac-11/9/testReport/ At this point it shows 256 failures vs. the approx. 230 failures against javac10 (with a little fluctuation between builds). Apparently, merging master & BETA_JAVA11 helped to reduce the failures. @Manoj, I would be great if you could identify and analyse the remaining difference. I suggest you start by comparing the "All Tests" summaries in https://hudson.eclipse.org/jdt/job/eclipse.jdt.core-run.javac-10/46/testReport/org.eclipse.jdt.core.tests.compiler.regression/ https://hudson.eclipse.org/jdt/job/eclipse.jdt.core-run.javac-11/9/testReport/org.eclipse.jdt.core.tests.compiler.regression/
setting a more realistic (=future) target.
Adjusting the title, since the infra-structure issues have been resolved, but we are left with new failures at 11.
Bulk move out of 4.11
missed this due to less bandwidth again - hope to reduce the failures in 4.13 in incrementally (or decr?) - moving to 4.13
Bulk move out of 4.14
Bulk move out of 4.19
Bulk move out of 4.20
Bulk move out of 4.22. If this is going to make it to 4.22, feel free to set the target back.
Bulk move out of 4.23
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant. -- The automated Eclipse Genie.
