Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 335517 - [e4] Tycho fails to execute tests on e4
Summary: [e4] Tycho fails to execute tests on e4
Status: RESOLVED FIXED
Alias: None
Product: z_Archived
Classification: Eclipse Foundation
Component: Mylyn (show other bugs)
Version: unspecified   Edit
Hardware: PC Linux
: P3 minor (vote)
Target Milestone: 3.5   Edit
Assignee: Steffen Pingel CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: 321278 336432
  Show dependency tree
 
Reported: 2011-01-26 17:10 EST by Steffen Pingel CLA
Modified: 2011-08-18 07:06 EDT (History)
2 users (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Steffen Pingel CLA 2011-01-26 17:10:51 EST 
Tests fail to startup with the error below in the log.

https://hudson.eclipse.org/hudson/job/mylyn-integration-e4.1/

org.eclipse.core.runtime.AssertionFailedException: null argument:applicationXMI argument missing
	at org.eclipse.core.runtime.Assert.isNotNull(Assert.java:85)
	at org.eclipse.e4.ui.internal.workbench.swt.E4Application.loadApplicationModel(E4Application.java:277)
	at org.eclipse.e4.ui.internal.workbench.swt.E4Application.createE4Workbench(E4Application.java:191)
	at org.eclipse.ui.internal.Workbench$3.run(Workbench.java:523)
	at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
	at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:516)
	at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149)
	at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:115)
	at org.codehaus.tycho.surefire.osgibooter.UITestApplication.runApplication(UITestApplication.java:21)
	at org.codehaus.tycho.surefire.osgibooter.AbstractUITestApplication.run(AbstractUITestApplication.java:109)
	at org.codehaus.tycho.surefire.osgibooter.UITestApplication.start(UITestApplication.java:27)
	at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196)
	at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:110)
	at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:79)
	at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:369)
	at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:179)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
	at java.lang.reflect.Method.invoke(Method.java:597)
	at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:622)
	at org.eclipse.equinox.launcher.Main.basicRun(Main.java:577)
	at org.eclipse.equinox.launcher.Main.run(Main.java:1410)
	at org.eclipse.equinox.launcher.Main.main(Main.java:1386)
Comment 1 Steffen Pingel CLA 2011-01-26 17:43:52 EST 
Fixed by adding explicit version constraints for the platform feature to the tests plug-in pom.
Comment 2 Remy Suen CLA 2011-01-26 17:45:55 EST 
(In reply to comment #1)
> Fixed by adding explicit version constraints for the platform feature to the
> tests plug-in pom.

Did you force them to be run on 3.7?
Comment 3 Steffen Pingel CLA 2011-01-26 18:18:13 EST 
No, forced the version constraints for org.eclipse.sdk.ide to be [4.1.0,4.2.0). Judging from the test failures it was indeed running on e4 ;).