Community
Participate
Working Groups
The following tests are failing after merging Java 10 with master: JavaSearchBugs9Tests.testBug528059_001() JavaElementDeltaTests.testChangeJRE9_8() ReconcilerTests.testConvertPrimitiveTypeArrayTypeArgument()
(In reply to Jay Arthanareeswaran from comment #0) > The following tests are failing after merging Java 10 with master: > > JavaElementDeltaTests.testChangeJRE9_8() I can't reproduce. Are you saying it fails on master? Which JRE? What's the failure message?
(In reply to Stephan Herrmann from comment #1) > (In reply to Jay Arthanareeswaran from comment #0) > > The following tests are failing after merging Java 10 with master: > > > > JavaElementDeltaTests.testChangeJRE9_8() > > I can't reproduce. Are you saying it fails on master? Which JRE? What's the > failure message? I was going to mention that that one was the least of the concern, but it was too late last night. Anyway, the problem is just the order of the entries - on my machine, the jclMin1.8 appears after the module entries rather than before. It happens with both JDK 10 (build 43) and a slightly older JDK 9. Perhaps a windows problem? I will take a look this one and others to provide more info.
JavaElementDeltaTests.testChangeJRE9_8() failed again on both Java9-enabled platforms: https://download.eclipse.org/eclipse/downloads/drops4/I20200215-1800/testresults/html/org.eclipse.jdt.core.tests.model_ep415I-unit-cen64-gtk3-java13_linux.gtk.x86_64_13.html https://download.eclipse.org/eclipse/downloads/drops4/I20200215-1800/testresults/html/org.eclipse.jdt.core.tests.model_ep415I-unit-cen64-gtk3-java11_linux.gtk.x86_64_11.html I locally tested a handful of JREs but never so the error locally. It's not a windows issue as the failures happened on cen64. Do we know which exact JRE those machines are using?
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.
