Comment 1 Dani Megert 2013-10-31 05:48:30 EDT

Failed again:
http://download.eclipse.org/eclipse/downloads/drops4/I20131030-1400/testresults/html/org.eclipse.core.tests.runtime_win32.win32.x86_7.0.html

Comment 2 Dani Megert 2014-01-21 11:52:37 EST

Failed again. This time in an M-build:

http://download.eclipse.org/eclipse/downloads/drops4/M20140117-0910/testresults/html/org.eclipse.core.tests.runtime_win32.win32.x86_7.0.html

Comment 3 Dani Megert 2014-05-20 03:30:31 EDT

And again, this time on Linux:
http://download.eclipse.org/eclipse/downloads/drops4/I20140519-2000/testresults/html/org.eclipse.core.tests.runtime_linux.gtk.x86_64_8.0.html

Comment 4 Dani Megert 2014-05-26 10:04:15 EDT

Again on Linux:
http://download.eclipse.org/eclipse/downloads/drops4/I20140525-2000/testresults/html/org.eclipse.core.tests.runtime_linux.gtk.x86_64_8.0.html

Comment 5 Dani Megert 2014-08-27 04:05:00 EDT

Failed again, this time on Windows:

http://download.eclipse.org/eclipse/downloads/drops4/N20140826-2000/testresults/html/org.eclipse.core.tests.runtime_win32.win32.x86_7.0.html

Comment 6 Szymon Ptaszkiewicz 2014-08-29 15:09:01 EDT

It just failed for me locally but I have no idea why yet.

Comment 7 Dani Megert 2014-09-03 04:14:46 EDT

It failed again:
http://download.eclipse.org/eclipse/downloads/drops4/I20140902-0800/testresults/html/org.eclipse.core.tests.runtime_win32.win32.x86_7.0.html

Comment 8 Szymon Ptaszkiewicz 2014-09-24 04:48:15 EDT

And again in N20140923-2000:

http://download.eclipse.org/eclipse/downloads/drops4/N20140923-2000/testresults/html/org.eclipse.core.tests.runtime_win32.win32.x86_7.0.html

Comment 9 Dani Megert 2014-10-01 03:53:39 EDT

Again in N20140930-2000.

Comment 10 Szymon Ptaszkiewicz 2014-10-02 04:59:11 EDT

(In reply to Dani Megert from comment #9)
> Again in N20140930-2000.

From the console output [1] we know that the job in the test started successfully, but it failed on this assertion:

!ENTRY org.eclipse.core.jobs 4 2 2014-09-30 21:52:35.218
!MESSAGE An internal error occurred during: "testSetProgressGroup".
!STACK 0
junit.framework.AssertionFailedError: Timeout after 51666ms waiting for status to change from RUNNING to WAIT_FOR_DONE
	at junit.framework.Assert.fail(Assert.java:57)
	at junit.framework.Assert.assertTrue(Assert.java:22)
	at org.eclipse.core.tests.harness.TestBarrier.doWaitForStatus(TestBarrier.java:88)
	at org.eclipse.core.tests.harness.TestBarrier.waitForStatus(TestBarrier.java:122)
	at org.eclipse.core.tests.harness.TestBarrier.waitForStatus(TestBarrier.java:160)
	at org.eclipse.core.tests.runtime.jobs.JobTest$24.run(JobTest.java:1288)
	at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)

while the test failed on this assertion:

junit.framework.AssertionFailedError: Timeout after 54797ms waiting for status to change from WAIT_FOR_START to RUNNING
	at org.eclipse.core.tests.harness.TestBarrier.doWaitForStatus(TestBarrier.java:88)
	at org.eclipse.core.tests.harness.TestBarrier.waitForStatus(TestBarrier.java:122)
	at org.eclipse.core.tests.harness.TestBarrier.waitForStatus(TestBarrier.java:160)
	at org.eclipse.core.tests.runtime.jobs.JobTest.testSetProgressGroup(JobTest.java:1309)
	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:134)
	at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:104)
	at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:380)
	at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:235)
	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:1465)
	at org.eclipse.equinox.launcher.Main.main(Main.java:1438)
	at org.eclipse.core.launcher.Main.main(Main.java:34)

[1] http://download.eclipse.org/eclipse/downloads/drops4/N20140930-2000/testresults/win32.win32.x86_7.0/org.eclipse.core.tests.runtime.AutomatedTests.txt

Comment 11 Szymon Ptaszkiewicz 2014-10-02 05:23:17 EDT

Both failures can be reproduced when using breakpoints and taking long breaks which is fine because timeout is better than deadlock. The question is why this test gives timeout so often even if the timeout threshold is set to 50 seconds. 50 seconds should more than sufficient for a job to start running after it was scheduled with 100 ms delay.

Comment 12 Szymon Ptaszkiewicz 2014-10-02 05:35:40 EDT

Maybe the hint is in the actual timeout value: 51666ms for the job and 54797ms for the test. Usually, both values are around 50000ms potentially with a small overhead like 100-200ms due to the way TestBarrier waits for a timeout: it should wait 500 ticks while each tick should take about 100ms. 54797ms is a bit too long.

Comment 13 Dani Megert 2014-11-18 04:18:16 EST

Failed again in N20141117-2000.

Comment 14 Dani Megert 2015-05-29 02:28:24 EDT

Failed again in I20150528-0700.

Comment 15 Dani Megert 2015-06-03 03:57:29 EDT

Failed again:
http://download.eclipse.org/eclipse/downloads/drops4/I20150602-2000/testresults/html/org.eclipse.core.tests.runtime_win32.win32.x86_7.0.html

Comment 16 David Williams 2015-10-30 05:27:42 EDT

Failed again, in Neon M3 candidate

http://download.eclipse.org/eclipse/downloads/drops4/I20151029-1100/testresults/xml/org.eclipse.core.tests.runtime_win32.win32.x86_8.0.xml

Should this test be disabled until new attempted fixes or debugging statements can be added?

Comment 17 Dani Megert 2015-12-11 04:35:34 EST

(In reply to David Williams from comment #16)
> Failed again, in Neon M3 candidate
> 
> http://download.eclipse.org/eclipse/downloads/drops4/I20151029-1100/testresults/xml/org.eclipse.core.tests.runtime_win32.win32.x86_8.0.xml
> 
> 
> Should this test be disabled until new attempted fixes or debugging
> statements can be added?

And again in Neon M4 candidate:

http://download.eclipse.org/eclipse/downloads/drops4/I20151209-2300/testresults/html/org.eclipse.core.tests.runtime_win32.win32.x86_8.0.html


Please take a look at this test.

Comment 18 Lars Vogel 2016-01-25 04:56:05 EST

Mass move to M6

Comment 19 Lars Vogel 2016-04-25 15:11:19 EDT

Mass move to 4.6 RC1. We might push out more to 4.7.

Comment 20 Dani Megert 2016-05-10 04:00:17 EDT

Failed again in I20160509-2000.

http://download.eclipse.org/eclipse/downloads/drops4/I20160509-2000/testresults/html/org.eclipse.core.tests.runtime_ep46I-unit-lin64_linux.gtk.x86_64_8.0.html

Comment 21 Dani Megert 2017-02-16 08:51:10 EST

Failed again in M20170215-0400.

Comment 22 Kalyan Prasad Tatavarthi 2017-09-14 11:35:51 EDT

Failed again in I20170913-2000

Comment 23 Eclipse Genie 2020-02-18 04:54:03 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. As such, we're closing this bug.

If you have further information on the current state of the bug, please add it and reopen this bug. 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.

--
The automated Eclipse Genie.