OK, after updating to the latest I-Build the tests can be executed again. Seems it was a bug in the M-Build.
Thanks for the help! On Fri, Apr 7, 2017 at 6:46 PM, Ed Merks <[email protected]> wrote: > Dirk, > > Mine came from http://download.eclipse.org/eclipse/updates/4.7-I-builds > today and that version earlier today was 3.12.0.v20170323-0108. > It's always so hard to find the repo containing a given Java file so that > one can look at the git history of the file. :-( We should have > something like the Oomph's IU indexing that we do for p2 repositories: but > you can find out where a given Java file is hosted in a git repository... > - 5.13 How to find a P2 repository at Eclipse using the Repository > Explorer > <https://wiki.eclipse.org/Eclipse_Oomph_Authoring#How_to_find_a_P2_repository_at_Eclipse_using_the_Repository_Explorer> > > On 07.04.2017 18:20, Dirk Fauth wrote: > > it is org.eclipse.core.resources_3.12.0.v20170307 > > On Fri, Apr 7, 2017 at 5:49 PM, Ed Merks <[email protected]> wrote: > >> Dirk, >> >> I have a very recent Oxygen build in my TP and I don't see that the >> ResourcesPlugin creates such a job. Perhaps it was removed again because >> it caused too many initialization problems... What version of the >> resource's bundle are you using? >> >> On 07.04.2017 16:55, Dirk Fauth wrote: >> >> Looks like a multi-threading issue. Not sure what introduced that or what >> is going wrong. >> >> - ResourcesPlugin#start(BundleContext) is started and the >> initWorkspaceJob is scheduled >> - ResourcesPlugin#getWorkspace() is called. The join() call in line 432 >> is called and returns directly >> - The exception comes up because workspace is still null >> >> The strange thing is that join() returns immediately, although the >> initWorkspaceJob was not executed. This leads to the incorrect state. But I >> can't explain why. Any ideas? >> >> On Fri, Apr 7, 2017 at 4:08 PM, Ed Merks <[email protected]> wrote: >> >>> Dirk, >>> >>> Use the debugger and set breakpoints. Is >>> org.eclipse.core.resources.ResourcesPlugin.start(BundleContext) >>> called? Normally it would be called very early and certainly before >>> anything can call ResourcePlugin.getWorkspace(). Is it successful >>> creating a workspace? If not, why not? If so, why is >>> ResourcesPlugin.workspace null later when getWorkspace is called? (Only >>> stop could do that...) >>> >>> In other words, try to figure out what's going wrong with the tools that >>> are available for that purpose. I can't reproduce your problem so I can >>> only guess at what might be wrong... >>> On 07.04.2017 15:38, Dirk Fauth wrote: >>> >>> Yes ... actually I started the test via Right click -> Run as -> JUnit >>> Plugin Test >>> >>> On Fri, Apr 7, 2017 at 2:00 PM, Ed Merks <[email protected]> wrote: >>> >>>> Dirk, >>>> >>>> Have you specified Workspace Data in the launcher? >>>> >>>> >>>> On 07.04.2017 11:53, Dirk Fauth wrote: >>>> >>>> Hi, >>>> >>>> I'm trying to execute the test cases locally in my current Oxygen IDE, >>>> for example the org.eclipse.ui.tests.api.IWorkbenchPageTest. But I get >>>> exceptions on starting the tests and I'm not able to solve them. >>>> java.lang.ExceptionInInitializerError at org.eclipse.emf.ecore.resource >>>> .impl.ResourceSetImpl.getURIConverter(ResourceSetImpl.java:499) at >>>> org.eclipse.emf.ecore.resource.impl.ResourceSetImpl.getResource(ResourceSetImpl.java:369) >>>> at >>>> org.eclipse.e4.ui.internal.workbench.ResourceHandler.getResource(ResourceHandler.java:286) >>>> at org.eclipse.e4.ui.internal.workbench.ResourceHandler.loadRes >>>> ource(ResourceHandler.java:262) at org.eclipse.e4.ui.internal.wor >>>> kbench.ResourceHandler.loadMostRecentModel(ResourceHandler.java:181) >>>> at org.eclipse.e4.ui.internal.workbench.swt.E4Application.loadA >>>> pplicationModel(E4Application.java:378) at >>>> org.eclipse.e4.ui.internal.workbench.swt.E4Application.creat >>>> eE4Workbench(E4Application.java:253) at org.eclipse.ui.internal.Workbe >>>> nch.lambda$3(Workbench.java:614) at org.eclipse.core.databinding.o >>>> bservable.Realm.runWithDefault(Realm.java:336) at >>>> org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:594) >>>> at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:148) >>>> at >>>> org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:145) >>>> at org.eclipse.pde.internal.junit.runtime.NonUIThreadTestApplic >>>> ation.runApp(NonUIThreadTestApplication.java:52) at >>>> org.eclipse.pde.internal.junit.runtime.UITestApplication.runApp(UITestApplication.java:43) >>>> at org.eclipse.pde.internal.junit.runtime.NonUIThreadTestApplic >>>> ation.start(NonUIThreadTestApplication.java:46) 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.adapt >>>> or.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(NativeMethodAccessorImpl.java:62) >>>> at >>>> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) >>>> at java.lang.reflect.Method.invoke(Method.java:498) at >>>> org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:653) at >>>> org.eclipse.equinox.launcher.Main.basicRun(Main.java:590) at >>>> org.eclipse.equinox.launcher.Main.run(Main.java:1499) at >>>> org.eclipse.equinox.launcher.Main.main(Main.java:1472) Caused by: >>>> java.lang.IllegalStateException: Workspace is closed. at >>>> org.eclipse.core.resources.ResourcesPlugin.getWorkspace(ResourcesPlugin.java:439) >>>> at >>>> org.eclipse.emf.ecore.plugin.EcorePlugin.getWorkspaceRoot(EcorePlugin.java:1131) >>>> at org.eclipse.emf.ecore.resource.impl.ExtensibleURIConverterIm >>>> pl.<clinit>(ExtensibleURIConverterImpl.java:393) ... 28 more >>>> The same applies if I try to start a test suite, Even when I try to use >>>> one of the available launch configurations. >>>> Am I missing something here? Our wiki page does not show any hints on >>>> that. >>>> Greez, >>>> Dirk >>>> >>>> _______________________________________________ >>>> e4-dev mailing [email protected] >>>> To change your delivery options, retrieve your password, or unsubscribe >>>> from this list, visithttps://dev.eclipse.org/mailman/listinfo/e4-dev >>>> >>>> _______________________________________________ e4-dev mailing list >>>> [email protected] To change your delivery options, retrieve your >>>> password, or unsubscribe from this list, visit >>>> https://dev.eclipse.org/mailman/listinfo/e4-dev >>> >>> _______________________________________________ >>> e4-dev mailing [email protected] >>> To change your delivery options, retrieve your password, or unsubscribe >>> from this list, visithttps://dev.eclipse.org/mailman/listinfo/e4-dev >>> >>> _______________________________________________ e4-dev mailing list >>> [email protected] To change your delivery options, retrieve your >>> password, or unsubscribe from this list, visit >>> https://dev.eclipse.org/mailman/listinfo/e4-dev >> >> _______________________________________________ >> e4-dev mailing [email protected] >> To change your delivery options, retrieve your password, or unsubscribe from >> this list, visithttps://dev.eclipse.org/mailman/listinfo/e4-dev >> >> _______________________________________________ e4-dev mailing list >> [email protected] To change your delivery options, retrieve your >> password, or unsubscribe from this list, visit >> https://dev.eclipse.org/mailman/listinfo/e4-dev > > _______________________________________________ > e4-dev mailing [email protected] > To change your delivery options, retrieve your password, or unsubscribe from > this list, visithttps://dev.eclipse.org/mailman/listinfo/e4-dev > > > _______________________________________________ > e4-dev mailing list > [email protected] > To change your delivery options, retrieve your password, or unsubscribe > from this list, visit > https://dev.eclipse.org/mailman/listinfo/e4-dev >
_______________________________________________ e4-dev mailing list [email protected] To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://dev.eclipse.org/mailman/listinfo/e4-dev
