Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Random Failing testProblemHover in genericeditor.tests.HoverTest #1808

Open
Wittmaxi opened this issue Apr 10, 2024 · 1 comment
Open

Random Failing testProblemHover in genericeditor.tests.HoverTest #1808

Wittmaxi opened this issue Apr 10, 2024 · 1 comment
Labels
bug Something isn't working test junit test related things

Comments

@Wittmaxi
Copy link
Contributor

Random Failing testProblemHover (org.eclipse.ui.genericeditor.tests.HoverTest)

Fails on Ubuntu

java.lang.AssertionError: null
	at org.junit.Assert.fail(Assert.java:89)
	at org.junit.Assert.assertTrue(Assert.java:42)
	at org.eclipse.ui.genericeditor.tests.HoverTest.testProblemHover(HoverTest.java:130)
	at java.base/jdk.internal.reflect.DirectMethodHandleAccessor.invoke(DirectMethodHandleAccessor.java:103)
	at java.base/java.lang.reflect.Method.invoke(Method.java:580)
	at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:59)
	at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
	at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:56)
	at org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
	at org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26)
	at org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27)
	at org.junit.rules.TestWatcher$1.evaluate(TestWatcher.java:61)
	at org.junit.runners.ParentRunner$3.evaluate(ParentRunner.java:306)
	at org.junit.runners.BlockJUnit4ClassRunner$1.evaluate(BlockJUnit4ClassRunner.java:100)
	at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:366)
	at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:103)
	at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:63)
	at org.junit.runners.ParentRunner$4.run(ParentRunner.java:331)
	at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:79)
	at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:329)
	at org.junit.runners.ParentRunner.access$100(ParentRunner.java:66)
	at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:293)
	at org.junit.runners.ParentRunner$3.evaluate(ParentRunner.java:306)
	at org.junit.runners.ParentRunner.run(ParentRunner.java:413)
	at org.junit.runners.Suite.runChild(Suite.java:128)
	at org.junit.runners.Suite.runChild(Suite.java:27)
	at org.junit.runners.ParentRunner$4.run(ParentRunner.java:331)
	at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:79)
	at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:329)
	at org.junit.runners.ParentRunner.access$100(ParentRunner.java:66)
	at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:293)
	at org.junit.runners.ParentRunner$3.evaluate(ParentRunner.java:306)
	at org.junit.runners.ParentRunner.run(ParentRunner.java:413)
	at org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:316)
	at org.apache.maven.surefire.junit4.JUnit4Provider.executeWithRerun(JUnit4Provider.java:240)
	at org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:214)
	at org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:155)
	at java.base/jdk.internal.reflect.DirectMethodHandleAccessor.invoke(DirectMethodHandleAccessor.java:103)
	at java.base/java.lang.reflect.Method.invoke(Method.java:580)
	at org.apache.maven.surefire.api.util.ReflectionUtils.invokeMethodWithArray2(ReflectionUtils.java:137)
	at org.apache.maven.surefire.booter.ProviderFactory$ProviderProxy.invoke(ProviderFactory.java:148)
	at org.apache.maven.surefire.booter.ProviderFactory.invokeProvider(ProviderFactory.java:88)
	at org.eclipse.tycho.surefire.osgibooter.OsgiSurefireBooter.run(OsgiSurefireBooter.java:140)
	at org.eclipse.tycho.surefire.osgibooter.AbstractUITestApplication$1.run(AbstractUITestApplication.java:42)
	at org.eclipse.e4.ui.internal.workbench.swt.E4Testable.lambda$1(E4Testable.java:127)
	at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:40)
	at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:132)
	at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:5040)
	at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:4520)
	at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$5.run(PartRenderingEngine.java:1151)
	at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:339)
	at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:1042)
	at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:152)
	at org.eclipse.ui.internal.Workbench.lambda$3(Workbench.java:639)
	at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:339)
	at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:546)
	at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:173)
	at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:152)
	at org.eclipse.tycho.surefire.osgibooter.UITestApplication.runApplication(UITestApplication.java:34)
	at org.eclipse.tycho.surefire.osgibooter.AbstractUITestApplication.run(AbstractUITestApplication.java:129)
	at org.eclipse.tycho.surefire.osgibooter.UITestApplication.start(UITestApplication.java:44)
	at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:208)
	at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:143)
	at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:109)
	at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:439)
	at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:271)
	at java.base/jdk.internal.reflect.DirectMethodHandleAccessor.invoke(DirectMethodHandleAccessor.java:103)
	at java.base/java.lang.reflect.Method.invoke(Method.java:580)
	at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:679)
	at org.eclipse.equinox.launcher.Main.basicRun(Main.java:616)
	at org.eclipse.equinox.launcher.Main.run(Main.java:1492)
	at org.eclipse.equinox.launcher.Main.main(Main.java:1465)
@Wittmaxi Wittmaxi added the bug Something isn't working label Apr 10, 2024
@Wittmaxi Wittmaxi mentioned this issue Apr 10, 2024
Merged
@jukzi jukzi added the test junit test related things label Apr 16, 2024
@jukzi
Copy link
Contributor

jukzi commented Apr 16, 2024

may relate to #926

This was referenced Jul 8, 2024
Merged
Merged
HeikoKlare added a commit to HeikoKlare/eclipse.platform.ui that referenced this issue Jul 16, 2024
@HeikoKlare
Improve and add assertions for random failing HoverTest eclipse-platf…
e9f9f2f 
…orm#926 eclipse-platform#1808

This contributes to fixing the randomly failing HoverTests:
- Removes unnecessary focus enforcing: The code checks for the text
editor having focus and afterwards uses different methods to force focus
to the widget's shell again. This is unnecessary and is only prone to
introduce further problems.
- Introduces further assertions: in order to better locate the cause of
the failing tests, assertions are added for the conditions, on which the
execution waits, to be actually fulfilled.

Contributes to
eclipse-platform#926
Contributes to
eclipse-platform#1808
@HeikoKlare HeikoKlare mentioned this issue Jul 16, 2024
Merged
HeikoKlare added a commit to HeikoKlare/eclipse.platform.ui that referenced this issue Jul 16, 2024
@HeikoKlare
Improve and add assertions for random failing HoverTest eclipse-platf…
82aec9d 
…orm#926 eclipse-platform#1808

This contributes to fixing the randomly failing HoverTests:
- Removes unnecessary focus enforcing: The code checks for the text
editor having focus and afterwards uses different methods to force focus
to the widget's shell again. This is unnecessary and is only prone to
introduce further problems.
- Introduces further assertions: in order to better locate the cause of
the failing tests, assertions are added for the conditions, on which the
execution waits, to be actually fulfilled.

Contributes to
eclipse-platform#926
Contributes to
eclipse-platform#1808
HeikoKlare added a commit to HeikoKlare/eclipse.platform.ui that referenced this issue Jul 16, 2024
@HeikoKlare
Improve and add assertions for random failing HoverTest eclipse-platf…
51fa1a8 
…orm#926 eclipse-platform#1808

This contributes to fixing the randomly failing HoverTests:
- Removes unnecessary focus enforcing: The code checks for the text
editor having focus and afterwards uses different methods to force focus
to the widget's shell again. This is unnecessary and is only prone to
introduce further problems.
- Introduces further assertions: in order to better locate the cause of
the failing tests, assertions are added for the conditions, on which the
execution waits, to be actually fulfilled.
- Adds a retry functionality for simulating the hover event.

Contributes to
eclipse-platform#926
Contributes to
eclipse-platform#1808
HeikoKlare added a commit to HeikoKlare/eclipse.platform.ui that referenced this issue Jul 16, 2024
@HeikoKlare
Improve and add assertions for random failing HoverTest eclipse-platf…
d00be4b 
…orm#926 eclipse-platform#1808

This contributes to fixing the randomly failing HoverTests:
- Removes unnecessary focus enforcing: The code checks for the text
editor having focus and afterwards uses different methods to force focus
to the widget's shell again. This is unnecessary and is only prone to
introduce further problems.
- Introduces further assertions: in order to better locate the cause of
the failing tests, assertions are added for the conditions, on which the
execution waits, to be actually fulfilled.
- Adds a retry functionality for simulating the hover event.

Contributes to
eclipse-platform#926
Contributes to
eclipse-platform#1808
HeikoKlare added a commit to HeikoKlare/eclipse.platform.ui that referenced this issue Jul 23, 2024
@HeikoKlare
Improve and add assertions for random failing HoverTest eclipse-platf…
058c185 
…orm#926 eclipse-platform#1808

This contributes to fixing the randomly failing HoverTests:
- Removes unnecessary focus enforcing: The code checks for the text
editor having focus and afterwards uses different methods to force focus
to the widget's shell again. This is unnecessary and is only prone to
introduce further problems.
- Introduces further assertions: in order to better locate the cause of
the failing tests, assertions are added for the conditions, on which the
execution waits, to be actually fulfilled.
- Adds a retry functionality for simulating the hover event.

Contributes to
eclipse-platform#926
Contributes to
eclipse-platform#1808
HeikoKlare added a commit to HeikoKlare/eclipse.platform.ui that referenced this issue Aug 7, 2024
@HeikoKlare
Improve and add assertions for random failing HoverTest eclipse-platf…
4183c63 
…orm#926 eclipse-platform#1808

This contributes to fixing the randomly failing HoverTests:
- Removes unnecessary focus enforcing: The code checks for the text
editor having focus and afterwards uses different methods to force focus
to the widget's shell again. This is unnecessary and is only prone to
introduce further problems.
- Introduces further assertions: in order to better locate the cause of
the failing tests, assertions are added for the conditions, on which the
execution waits, to be actually fulfilled.
- Adds a retry functionality for simulating the hover event.

Contributes to
eclipse-platform#926
Contributes to
eclipse-platform#1808
HeikoKlare added a commit to HeikoKlare/eclipse.platform.ui that referenced this issue Aug 19, 2024
@HeikoKlare
Improve and add assertions for random failing HoverTest eclipse-platf…
972bda5 
…orm#926 eclipse-platform#1808

This contributes to fixing the randomly failing HoverTests:
- Removes unnecessary focus enforcing: The code checks for the text
editor having focus and afterwards uses different methods to force focus
to the widget's shell again. This is unnecessary and is only prone to
introduce further problems.
- Introduces further assertions: in order to better locate the cause of
the failing tests, assertions are added for the conditions, on which the
execution waits, to be actually fulfilled.
- Adds a retry functionality for simulating the hover event.

Contributes to
eclipse-platform#926
Contributes to
eclipse-platform#1808
HeikoKlare added a commit to HeikoKlare/eclipse.platform.ui that referenced this issue Sep 4, 2024
@HeikoKlare
Improve and add assertions for random failing HoverTest eclipse-platf…
414767f 
…orm#926 eclipse-platform#1808

This contributes to fixing the randomly failing HoverTests:
- Removes unnecessary focus enforcing: The code checks for the text
editor having focus and afterwards uses different methods to force focus
to the widget's shell again. This is unnecessary and is only prone to
introduce further problems.
- Introduces further assertions: in order to better locate the cause of
the failing tests, assertions are added for the conditions, on which the
execution waits, to be actually fulfilled.
- Adds a retry functionality for simulating the hover event.

Contributes to
eclipse-platform#926
Contributes to
eclipse-platform#1808
HeikoKlare added a commit to HeikoKlare/eclipse.platform.ui that referenced this issue Nov 7, 2024
@HeikoKlare
Improve and add assertions for random failing HoverTest eclipse-platf…
854004e 
…orm#926 eclipse-platform#1808

This contributes to fixing the randomly failing HoverTests:
- Removes unnecessary focus enforcing: The code checks for the text
editor having focus and afterwards uses different methods to force focus
to the widget's shell again. This is unnecessary and is only prone to
introduce further problems.
- Introduces further assertions: in order to better locate the cause of
the failing tests, assertions are added for the conditions, on which the
execution waits, to be actually fulfilled.
- Adds a retry functionality for simulating the hover event.

Contributes to
eclipse-platform#926
Contributes to
eclipse-platform#1808
HeikoKlare added a commit to HeikoKlare/eclipse.platform.ui that referenced this issue Nov 7, 2024
@HeikoKlare
Improve and add assertions for random failing HoverTest eclipse-platf…
49db425 
…orm#926 eclipse-platform#1808

This contributes to fixing the randomly failing HoverTests:
- Removes unnecessary focus enforcing: The code checks for the text
editor having focus and afterwards uses different methods to force focus
to the widget's shell again. This is unnecessary and is only prone to
introduce further problems.
- Introduces further assertions: in order to better locate the cause of
the failing tests, assertions are added for the conditions, on which the
execution waits, to be actually fulfilled.
- Adds a retry functionality for simulating the hover event.

Contributes to
eclipse-platform#926
Contributes to
eclipse-platform#1808
HeikoKlare added a commit to HeikoKlare/eclipse.platform.ui that referenced this issue Nov 8, 2024
@HeikoKlare
Improve and add assertions for random failing HoverTest eclipse-platf…
fedc0fd 
…orm#926 eclipse-platform#1808

This contributes to fixing the randomly failing HoverTests:
- Removes unnecessary focus enforcing: The code checks for the text
editor having focus and afterwards uses different methods to force focus
to the widget's shell again. This is unnecessary and is only prone to
introduce further problems.
- Introduces further assertions: in order to better locate the cause of
the failing tests, assertions are added for the conditions, on which the
execution waits, to be actually fulfilled.
- Adds a retry functionality for simulating the hover event.

Contributes to
eclipse-platform#926
Contributes to
eclipse-platform#1808
HeikoKlare added a commit to HeikoKlare/eclipse.platform.ui that referenced this issue Nov 8, 2024
@HeikoKlare
Improve and add assertions for random failing HoverTest eclipse-platf…
a97b1da 
…orm#926 eclipse-platform#1808

This contributes to fixing the randomly failing HoverTests:
- Removes unnecessary focus enforcing: The code checks for the text
editor having focus and afterwards uses different methods to force focus
to the widget's shell again. This is unnecessary and is only prone to
introduce further problems.
- Introduces further assertions: in order to better locate the cause of
the failing tests, assertions are added for the conditions, on which the
execution waits, to be actually fulfilled.
- Adds a retry functionality for simulating the hover event.

Contributes to
eclipse-platform#926
Contributes to
eclipse-platform#1808
HeikoKlare added a commit that referenced this issue Nov 8, 2024
@HeikoKlare
Improve and add assertions for random failing HoverTest #926 #1808
2c07aa7 
This contributes to fixing the randomly failing HoverTests:
- Removes unnecessary focus enforcing: The code checks for the text
editor having focus and afterwards uses different methods to force focus
to the widget's shell again. This is unnecessary and is only prone to
introduce further problems.
- Introduces further assertions: in order to better locate the cause of
the failing tests, assertions are added for the conditions, on which the
execution waits, to be actually fulfilled.
- Adds a retry functionality for simulating the hover event.

Contributes to
#926
Contributes to
#1808
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug Something isn't working test junit test related things
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@Wittmaxi @jukzi