Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 343164 - Test failures in testDisableDecorator, testContributorResourceAdapter, testDecoratorCacheIsDisposed, testActivateSameStack
Summary: Test failures in testDisableDecorator, testContributorResourceAdapter, testDe...
Status: CLOSED WONTFIX
Alias: None
Product: Platform
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 3.7   Edit
Hardware: PC Windows All
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Platform UI Triaged CLA
QA Contact:
URL:
Whiteboard: stalebug
Keywords:
Depends on:
Blocks:
 
Reported: 2011-04-18 10:59 EDT by Oleg Besedin CLA
Modified: 2019-11-14 02:15 EST (History)
2 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Oleg Besedin CLA 2011-04-18 10:59:31 EDT
We had 4 tests failed in the N20110416-2000 build on the Windows machine.

2 test failures are in the processing of SWT event loops
2 test failures seems to be related to resources

I am unable to reproduce those failures locally and the next N-build (N20110417-2000) had all tests pass.

This is likely an aberration of a test machine. I am opening this bug to have stack traces just in case those failures will show up again.

===

Failed to execute runnable (org.eclipse.core.runtime.AssertionFailedException: null argument:)

org.eclipse.swt.SWTException: Failed to execute runnable (org.eclipse.core.runtime.AssertionFailedException: null argument:)
at org.eclipse.swt.SWT.error(SWT.java:4277)
at org.eclipse.swt.SWT.error(SWT.java:4192)
at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:137)
at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:4138)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3755)
at org.eclipse.ui.tests.harness.util.UITestCase.processEvents(UITestCase.java:223)
at org.eclipse.ui.tests.harness.util.UITestCase.waitOnShell(UITestCase.java:291)
at org.eclipse.ui.tests.harness.util.UITestCase.openTestWindow(UITestCase.java:273)
at org.eclipse.ui.tests.harness.util.UITestCase.openTestWindow(UITestCase.java:263)
at org.eclipse.ui.tests.navigator.AbstractNavigatorTest.showNav(AbstractNavigatorTest.java:75)
at org.eclipse.ui.tests.decorators.BadIndexDecoratorTestCase.doSetUp(BadIndexDecoratorTestCase.java:36)
at org.eclipse.ui.tests.harness.util.UITestCase.setUp(UITestCase.java:180)

===

Adaptable test 4 has failed for object org.eclipse.ui.tests.menus.ObjectContributionClasses$CResourceOnly@d2438d

junit.framework.AssertionFailedError: Adaptable test 4 has failed for object org.eclipse.ui.tests.menus.ObjectContributionClasses$CResourceOnly@d2438d
at org.eclipse.ui.tests.decorators.DecoratorAdaptableTests.assertDecorated(DecoratorAdaptableTests.java:56)
at org.eclipse.ui.tests.decorators.DecoratorAdaptableTests.testContributorResourceAdapter(DecoratorAdaptableTests.java:175)

===

Failed to execute runnable (org.eclipse.core.runtime.AssertionFailedException: null argument:)

org.eclipse.swt.SWTException: Failed to execute runnable (org.eclipse.core.runtime.AssertionFailedException: null argument:)
at org.eclipse.swt.SWT.error(SWT.java:4277)
at org.eclipse.swt.SWT.error(SWT.java:4192)
at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:137)
at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:4138)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3755)
at org.eclipse.ui.tests.harness.util.UITestCase.processEvents(UITestCase.java:223)
at org.eclipse.ui.tests.harness.util.UITestCase.doTearDown(UITestCase.java:217)
at org.eclipse.ui.tests.zoom.ZoomTestCase.doTearDown(ZoomTestCase.java:79)
at org.eclipse.ui.tests.harness.util.UITestCase.tearDown(UITestCase.java:203)

===
Comment 1 Lars Vogel CLA 2019-11-14 02:15:12 EST
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.

If the bug is still relevant, please remove the "stalebug" whiteboard tag.