Community
Participate
Working Groups
java.lang.Exception: Could not find plugin "org.eclipse.pde.api.tools.tests" org.eclipse.test.EclipseTestRunner$TestFailedException: java.lang.Exception: Could not find plugin "org.eclipse.pde.api.tools.tests" at org.eclipse.test.EclipseTestRunner.runFailed(EclipseTestRunner.java:625) at org.eclipse.test.EclipseTestRunner.getTest(EclipseTestRunner.java:579) at org.eclipse.test.EclipseTestRunner.<init>(EclipseTestRunner.java:562) at org.eclipse.test.EclipseTestRunner.run(EclipseTestRunner.java:344) at org.eclipse.test.CoreTestApplication.runTests(CoreTestApplication.java:38) at org.eclipse.test.CoreTestApplication.run(CoreTestApplication.java:34) at org.eclipse.equinox.internal.app.EclipseAppContainer.callMethodWithException(EclipseAppContainer.java:587) at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:198) at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:134) at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:104) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:388) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:243)
Also I don't see API tools related preference pages.
Let's wait for I20180807-0350 results before investigating.
BTW, can it be caused by asm update in http://git.eclipse.org/c/platform/eclipse.platform.releng.aggregator.git/commit/?id=2752e40799dc6ec76ff8032cd84054006ce23b98 ?
(In reply to Vikas Chandra from comment #1) > Also I don't see API tools related preference pages. How can that be? Is there an exception in the .log?
Which preference pages are missing for you ? I have API baselines|Errors/warnings|Use scans.
Created attachment 275304 [details] Log from local mvn clean verify in pde.ui
(In reply to Alexander Kurtakov from comment #6) > Created attachment 275304 [details] > Log from local mvn clean verify in pde.ui So yes, it's coming from asm update according to this log.
(In reply to Alexander Kurtakov from comment #5) > Which preference pages are missing for you ? I have API > baselines|Errors/warnings|Use scans. Same here with I20180807-0350 and also I20180806-2000. Vikas?
For the record - apitools run fine with Java 10 on my machine. So the latest asm update introduced this dependency on Java 9.
(In reply to Alexander Kurtakov from comment #9) > For the record - apitools run fine with Java 10 on my machine. So the latest > asm update introduced this dependency on Java 9. I can confirm that API Tools no longer works with JRE < 10. This is a no go. JRE 8 is a supported target platform for 4.9.
Probably same reason as bug 537751.
Could this also be the reason behind today's failures in jdt-core-gerrit? 16:23:34 [INFO] Command line: 16:23:34 [/opt/public/common/jdk1.8.0_x64-latest/jre/bin/java, -jar, /jobs/genie.jdt/eclipse.jdt.core-Gerrit/workspace/.repository/p2/osgi/bundle/org.eclipse.equinox.launcher/1.5.100.v20180611-1436/org.eclipse.equinox.launcher-1.5.100.v20180611-1436.jar, -install, /jobs/genie.jdt/eclipse.jdt.core-Gerrit/workspace/org.eclipse.jdt.annotation/target/eclipserun-work, -configuration, /jobs/genie.jdt/eclipse.jdt.core-Gerrit/workspace/org.eclipse.jdt.annotation/target/eclipserun-work/configuration, -data, target/apibuild-workspace, -application, org.eclipse.ant.core.antRunner, -buildfile, target/.apibuild.xml] 16:23:34 Picked up JAVA_TOOL_OPTIONS: -Xmx2G -Djava.io.tmpdir=/tmp/genie.jdt 16:23:35 Buildfile: target/.apibuild.xml 16:23:35 16:23:35 apigen: 16:23:36 16:23:36 BUILD FAILED 16:23:36 /jobs/genie.jdt/eclipse.jdt.core-Gerrit/workspace/org.eclipse.jdt.annotation/target/.apibuild.xml:10: Problem: failed to create task or type apitooling.apigeneration 16:23:36 Cause: The name is undefined. 16:23:36 Action: Check the spelling. 16:23:36 Action: Check that any custom tasks/types have been declared. 16:23:36 Action: Check that any <presetdef>/<macrodef> declarations have taken place. (from https://ci.eclipse.org/jdt/job/eclipse.jdt.core-Gerrit/1109/console )
New Gerrit change created: https://git.eclipse.org/r/127160
(In reply to Stephan Herrmann from comment #12) > Could this also be the reason behind today's failures in jdt-core-gerrit? > > > (from https://ci.eclipse.org/jdt/job/eclipse.jdt.core-Gerrit/1109/console ) Yes, I see the same in the gerrit build for the change I submitted above to fix this mess: https://ci.eclipse.org/platform/job/eclipse.platform.releng.aggregator-Gerrit/470/console Which I suppose means the I-build repo used by tycho-eclipse-run-plugin is broken: http://download.eclipse.org/eclipse/updates/4.9-I-builds/I20180807-0350/ Alex/Dani: Is there any chance we can black-list that I-build? Or must we temporarily hard-code the "eclipserun-repo" in the parent pom?
Gerrit change https://git.eclipse.org/r/127160 was merged to [master]. Commit: http://git.eclipse.org/c/platform/eclipse.platform.releng.aggregator.git/commit/?id=999120b2087a527d915882349b3d39d30ca483d8
(In reply to Mat Booth from comment #14) > (In reply to Stephan Herrmann from comment #12) > > Could this also be the reason behind today's failures in jdt-core-gerrit? > > > > > > (from https://ci.eclipse.org/jdt/job/eclipse.jdt.core-Gerrit/1109/console ) > > Yes, I see the same in the gerrit build for the change I submitted above to > fix this mess: > > https://ci.eclipse.org/platform/job/eclipse.platform.releng.aggregator- > Gerrit/470/console > > Which I suppose means the I-build repo used by tycho-eclipse-run-plugin is > broken: > > http://download.eclipse.org/eclipse/updates/4.9-I-builds/I20180807-0350/ > > Alex/Dani: > > Is there any chance we can black-list that I-build? I've marked the bug as unstable which removes it from the composite I-build repo. > > Or must we temporarily hard-code the "eclipserun-repo" in the parent pom? No, don't do that it should be fine now.
http://download.eclipse.org/eclipse/downloads/drops4/I20180807-2000/testresults/html/org.eclipse.pde.api.tools.tests_ep49I-unit-mac64_macosx.cocoa.x86_64_8.0.html The tests run fine here. I am downloading the build to test it further.
Verified comment#0 and comment#1 on Version: 4.9 Build id: I20180807-2000
(In reply to Vikas Chandra from comment #18) > Verified comment#0 and comment#1 on > Version: 4.9 > Build id: I20180807-2000 Also verified with that build.
