| Re: [cross-project-issues-dev] running SWTBot tests with Buckminster on hudson.eclipse.org |
Nicolas, I applied the patch locally and was able to run our SWTBot tests on my machine again using an Indigo M6 installation and a JUnitPlugin-Test configuration with Run in UI thread set to false. The error you mentioned didn’t appear in my use case. How did you get the patch applied on Hudson? Michael From: cross-project-issues-dev-bounces@xxxxxxxxxxx [mailto:cross-project-issues-dev-bounces@xxxxxxxxxxx] On Behalf Of Nicolas Bros Hi, I'm trying to run our SWTBot tests with Buckminster. I have found that I cannot use the SWTBot launch configuration (org.eclipse.swtbot.eclipse.ui.launcher.JunitLaunchConfig) [1] because it cannot be used in Buckminster headless. So, I'm using "org.eclipse.pde.ui.JunitLaunchConfig" instead, with run_in_ui_thread = false, and with a patch that fixes the regression in 3.7 when run_in_ui_thread is false [2]. But I'm stuck on this error: An error occurred while automatically activating bundle org.eclipse.ui.workbench Which then causes : org.eclipse.core.runtime.CoreException: Plug-in "org.eclipse.ui.ide.application" was unable to instantiate class "org.eclipse.ui.internal.ide.application.IDEApplication". (these errors appear in the log in "workspace/.metadata/.plugins/org.eclipse.pde.core/AllUITests/1302092609229.log") Yet both the SWT plug-in and its platform-specific fragment are in my target platform: org.eclipse.swt.gtk.linux.x86_64_3.7.0.v3724c.jar org.eclipse.swt_3.7.0.v3724c.jar I checked, and SWTError is in jar org.eclipse.swt.gtk.linux.x86_64_3.7.0.v3724c.jar. And I have "-os linux -ws gtk -arch x86_64" in my log, so it would seem to match. And I have no message in my log about an unresolved SWT jar. Has anyone successfully run SWTBot tests with Buckminster on hudson.eclipse.org? [2] https://bugs.eclipse.org/bugs/attachment.cgi?id=192617 |