Community
Participate
Working Groups
I ran the UI tests (Eclipse automated tests) on HP-UX. I saw following 5 test cases are failing. 1) drag Navigator to out of the window 2) drag Navigator folder to out of the window 3) drag Problems to out of the window 4) drag Problems folder to out of the window 5) testPushdown Can you please look at this?. I have also attached the test result with this bug
Created attachment 25602 [details] UI test result
There are two problems here. The problem with the first four failures is that these tests assert whether you can detach a view from the workbench window. This operation isn't supported on Motif so the tests fail. We only recently started running the automated tests on platforms that don't support this feature (such as OS X) so it took us awhile to address the issue. The latest tests in the 3.2 stream should fix this problem - these tests are omitted when the support is not available. The last test failure is due to the fact that our font support on Motif allows for multiple font data objects for each font object. Our test doesn't take that into account. This indicates a bad test as opposed to a real failure. I will take a look into fixing this test for 3.2.
I have seen sometime 'testOverwritePerspective' & 'testNoValFont' are failing. Is it also related with font problem? Thanks, JP
testNoValFont is almost certainly the same font problem. testOverwritePerspective, however, is something new. Do you have a stack trace for this failure?
Yes. I have liste the stack trace for 'testOverwritePerspective' here. I hope it helps. Warning: Label {A perspective with the name 'Dummy Perspective' already exists. Do you want to overwrite?} Actual Width -> 529 Recommended Width -> 566 junit.framework.AssertionFailedError: Warning: Label {A perspective with the name 'Dummy Perspective' already exists. Do you want to overwrite?} Actual Width -> 529 Recommended Width -> 566 at org.eclipse.ui.tests.util.DialogCheck.verifyLabelText(DialogCheck.java:192) at org.eclipse.ui.tests.util.DialogCheck.verifyCompositeText (DialogCheck.java:128) at org.eclipse.ui.tests.util.DialogCheck.assertDialogTexts(DialogCheck.java:84) at org.eclipse.ui.tests.dialogs.UIMessageDialogsAuto.testOverwritePerspective (UIMessageDialogsAuto.java:213) at org.eclipse.test.EclipseTestRunner.run(EclipseTestRunner.java:313) at org.eclipse.test.EclipseTestRunner.run(EclipseTestRunner.java:199) at org.eclipse.test.UITestApplication$3.run(UITestApplication.java:188) at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35) at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:123) at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:3037) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:2751) at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:1699) at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:1663) at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:367) at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:143) at org.eclipse.ui.internal.ide.IDEApplication.run(IDEApplication.java:103) at org.eclipse.test.UITestApplication.runApplication (UITestApplication.java:131) at org.eclipse.test.UITestApplication.run(UITestApplication.java:58) at org.eclipse.core.internal.runtime.PlatformActivator$1.run (PlatformActivator.java:226) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:376) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:163) at org.eclipse.core.launcher.Main.invokeFramework(Main.java:334) at org.eclipse.core.launcher.Main.basicRun(Main.java:278) at org.eclipse.core.launcher.Main.run(Main.java:973) at org.eclipse.core.launcher.Main.main(Main.java:948)
Susan is now responsible for watching the [Themes] category.
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.
Motif is not supported for years.
