Bug 415878 - JobTest.testJoinFailingListener failed
Summary: JobTest.testJoinFailingListener failed
Status: CLOSED WONTFIX
Alias: None
Product: Platform
Classification: Eclipse Project
Component: Runtime (show other bugs)
Version: 4.4   Edit
Hardware: PC Linux-GTK
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: platform-runtime-inbox CLA
QA Contact:
URL:
Whiteboard: stalebug
Keywords: test
Depends on:
Blocks: 51538
  Show dependency tree
 
Reported: 2013-08-26 10:06 EDT by Dani Megert CLA
Modified: 2019-11-27 07:27 EST (History)
1 user (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Dani Megert CLA 2013-08-26 10:06:52 EDT
N20130825-2000.

http://download.eclipse.org/eclipse/downloads/drops4/N20130825-2000/testresults/html/org.eclipse.core.tests.runtime_linux.gtk.x86_6.0.html


Timeout after 10502ms waiting for status to change from START to DONE

junit.framework.AssertionFailedError: Timeout after 10502ms waiting for status to change from START to DONE
at org.eclipse.core.tests.harness.TestBarrier.doWaitForStatus(TestBarrier.java:88)
at org.eclipse.core.tests.harness.TestBarrier.waitForStatus(TestBarrier.java:114)
at org.eclipse.core.tests.runtime.jobs.JobTest.testJoinFailingListener(JobTest.java:882)
at org.eclipse.test.EclipseTestRunner.run(EclipseTestRunner.java:655)
at org.eclipse.test.EclipseTestRunner.run(EclipseTestRunner.java:310)
at org.eclipse.test.CoreTestApplication.runTests(CoreTestApplication.java:36)
at org.eclipse.test.CoreTestApplication.run(CoreTestApplication.java:32)
at org.eclipse.equinox.internal.app.EclipseAppContainer.callMethodWithException(EclipseAppContainer.java:587)
at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:198)
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:109)
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:80)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:372)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:226)
at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:636)
at org.eclipse.equinox.launcher.Main.basicRun(Main.java:591)
at org.eclipse.equinox.launcher.Main.run(Main.java:1450)
at org.eclipse.equinox.launcher.Main.main(Main.java:1426)
at org.eclipse.core.launcher.Main.main(Main.java:34)
Comment 1 Dani Megert CLA 2013-10-18 05:07:35 EDT
Failed again in N20131017-2000.
Comment 2 Dani Megert CLA 2013-11-22 04:17:56 EST
Failed again in N20131121-2000, again Linux.
Comment 3 Dani Megert CLA 2014-01-13 05:17:18 EST
Failed again in N20140110-2000 (Linux):

Timeout after 10503ms waiting for status to change from START to DONE

junit.framework.AssertionFailedError: Timeout after 10503ms waiting for status to change from START to DONE
at org.eclipse.core.tests.harness.TestBarrier.doWaitForStatus(TestBarrier.java:88)
at org.eclipse.core.tests.harness.TestBarrier.waitForStatus(TestBarrier.java:114)
at org.eclipse.core.tests.runtime.jobs.JobTest.testJoinFailingListener(JobTest.java:882)
at org.eclipse.test.EclipseTestRunner.run(EclipseTestRunner.java:657)
at org.eclipse.test.EclipseTestRunner.run(EclipseTestRunner.java:310)
at org.eclipse.test.CoreTestApplication.runTests(CoreTestApplication.java:36)
at org.eclipse.test.CoreTestApplication.run(CoreTestApplication.java:32)
at org.eclipse.equinox.internal.app.EclipseAppContainer.callMethodWithException(EclipseAppContainer.java:587)
at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:198)
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:109)
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:80)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:372)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:226)
at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:636)
at org.eclipse.equinox.launcher.Main.basicRun(Main.java:591)
at org.eclipse.equinox.launcher.Main.run(Main.java:1450)
at org.eclipse.equinox.launcher.Main.main(Main.java:1426)
at org.eclipse.core.launcher.Main.main(Main.java:34)
Comment 4 Dani Megert CLA 2014-02-05 03:27:33 EST
Failed again in N20140204-2000 (Linux):

Timeout after 10506ms waiting for status to change from START to DONE

junit.framework.AssertionFailedError: Timeout after 10506ms waiting for status to change from START to DONE
at org.eclipse.core.tests.harness.TestBarrier.doWaitForStatus(TestBarrier.java:88)
at org.eclipse.core.tests.harness.TestBarrier.waitForStatus(TestBarrier.java:114)
at org.eclipse.core.tests.runtime.jobs.JobTest.testJoinFailingListener(JobTest.java:882)
at org.eclipse.test.EclipseTestRunner.run(EclipseTestRunner.java:657)
at org.eclipse.test.EclipseTestRunner.run(EclipseTestRunner.java:310)
at org.eclipse.test.CoreTestApplication.runTests(CoreTestApplication.java:36)
at org.eclipse.test.CoreTestApplication.run(CoreTestApplication.java:32)
at org.eclipse.equinox.internal.app.EclipseAppContainer.callMethodWithException(EclipseAppContainer.java:587)
at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:198)
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:109)
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:80)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:372)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:226)
at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:648)
at org.eclipse.equinox.launcher.Main.basicRun(Main.java:603)
at org.eclipse.equinox.launcher.Main.run(Main.java:1462)
at org.eclipse.equinox.launcher.Main.main(Main.java:1438)
at org.eclipse.core.launcher.Main.main(Main.java:34)
Comment 5 Lars Vogel CLA 2019-11-27 07:27:23 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.