Skip to main content


Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » Eclipse Projects » RCP Testing Tool » Nightly runner (2.2.0) fails with target platform initialization
Nightly runner (2.2.0) fails with target platform initialization [message #1755208] Wed, 01 March 2017 07:52 Go to next message
Andreas Falter is currently offline Andreas FalterFriend
Messages: 15
Registered: February 2015
Junior Member
Hi,

because of some problems with the current stable 2.1.0 runner when running from Jenkins, I tried to switch to the nightly runner.

Unfortunately, with the same test project and AUT, the nightly runner fails to start while initializing the target platform. I compared the runner log file against the one when running with 2.1.0 runner, but the reported errors there are the same.

There are some unresolved dependencies (from runner), which seem not to be a problem in 2.1.0, and there is one message about multiple versions of the same bundle in our AUT, which did not make the runner fail with 2.1.0 (because we reference plugins always with versions in the application).

Is there a change in runner 2.2.0 that now will cause the initialization to fail because of these messages?

Log file is attached, the root exception is:
!ENTRY org.eclipse.osgi 4 0 2017-03-01 08:43:59.665
!MESSAGE Application error
!STACK 1
org.eclipse.core.runtime.CoreException: Target platform initialization failed
at org.eclipse.rcptt.internal.launching.ext.Q7TargetPlatformManager.createTargetPlatform(Q7TargetPlatformManager.java:135)
at org.eclipse.rcptt.runner.util.TargetPlatformChecker.initializeTargetPlatform(TargetPlatformChecker.java:113)
at org.eclipse.rcptt.runner.util.TargetPlatformChecker.initAndCheckTargetPlatform(TargetPlatformChecker.java:69)
at org.eclipse.rcptt.runner.HeadlessRunner.performCoolThings(HeadlessRunner.java:48)
at org.eclipse.rcptt.runner.HeadlessRunnerApp.start(HeadlessRunnerApp.java:54)
at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196)
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)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:673)
at org.eclipse.equinox.launcher.Main.basicRun(Main.java:610)
at org.eclipse.equinox.launcher.Main.run(Main.java:1519)
at org.eclipse.equinox.launcher.Main.main(Main.java:1492)
Caused by: java.lang.NullPointerException: Can't find dependencies for platform 3.6.0
at org.eclipse.rcptt.internal.launching.ext.Q7TargetPlatformInitializer.collectQ7Information(Q7TargetPlatformInitializer.java:305)
at org.eclipse.rcptt.internal.launching.ext.Q7TargetPlatformInitializer.getInfo(Q7TargetPlatformInitializer.java:272)
at org.eclipse.rcptt.internal.launching.ext.Q7TargetPlatformInitializer.initialize(Q7TargetPlatformInitializer.java:103)
at org.eclipse.rcptt.internal.launching.ext.Q7TargetPlatformManager.createTargetPlatform(Q7TargetPlatformManager.java:128)
... 17 more
  • Attachment: runner.log
    (Size: 22.04KB, Downloaded 59 times)
Re: Nightly runner (2.2.0) fails with target platform initialization [message #1759344 is a reply to message #1755208] Mon, 10 April 2017 16:58 Go to previous messageGo to next message
Andrey Sobolev is currently offline Andrey SobolevFriend
Messages: 74
Registered: February 2015
Member
Hi,

Did you applications is based on Eclipse 3.6?
It seems we miss a 3.6 dependencies in RCPTT installations since 2.2.
Do you plan to migrate to some new Eclipse platform version?

Thanks,
Andrey.
Re: Nightly runner (2.2.0) fails with target platform initialization [message #1760348 is a reply to message #1759344] Wed, 26 April 2017 08:23 Go to previous messageGo to next message
Andreas Falter is currently offline Andreas FalterFriend
Messages: 15
Registered: February 2015
Junior Member
Hi Andrey,

yes, our application still uses 3.6.2 as target platform. I think we will update to some recent 4.x version in the future, but I fear we will stick to 3.6.2 at least for a year or even more.

Would it be possible to manually add the missing dependencies to local 2.2.0 installations? Or is there a chance you can fix this before the offical 2.2 release?

Thanks and regards,
Andreas
Re: Nightly runner (2.2.0) fails with target platform initialization [message #1768265 is a reply to message #1760348] Sun, 16 July 2017 09:41 Go to previous messageGo to next message
jabin faith is currently offline jabin faithFriend
Messages: 1
Registered: July 2017
Junior Member
HI,

Our application uses 3.6.2 as target platform.
How to add manually the missing dependencies
Re: Nightly runner (2.2.0) fails with target platform initialization [message #1770244 is a reply to message #1768265] Wed, 09 August 2017 10:22 Go to previous message
Viktoria Dlugopolskaya is currently offline Viktoria DlugopolskayaFriend
Messages: 124
Registered: March 2017
Senior Member
Hi Andreas, Jabin,

We've added 3.6 to supported platforms in RCPTT 2.3.0
You can download latest nightly build here: https://eclipse.org/rcptt/download/
Previous Topic:AUT Connection Error
Next Topic:right click not being recorded correctly
Goto Forum:
  


Current Time: Mon Oct 22 03:08:18 GMT 2018

Powered by FUDForum. Page generated in 0.01855 seconds
.:: Contact :: Home ::.

Powered by: FUDforum 3.0.2.
Copyright ©2001-2010 FUDforum Bulletin Board Software

Back to the top