Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 318746 - Test failure in YieldTest.testResumingThreadJobIsNotRescheduled
Summary: Test failure in YieldTest.testResumingThreadJobIsNotRescheduled
Status: RESOLVED FIXED
Alias: None
Product: Platform
Classification: Eclipse Project
Component: Runtime (show other bugs)
Version: 3.7   Edit
Hardware: PC Windows XP
: P3 normal (vote)
Target Milestone: 3.7 M1   Edit
Assignee: John Arthorne CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: 320342
  Show dependency tree
 
Reported: 2010-07-02 11:30 EDT by John Arthorne CLA
Modified: 2010-07-19 19:52 EDT (History)
1 user (show)

See Also:

Attachments
Fix to the test (1.30 KB, patch)
2010-07-19 17:58 EDT, John Arthorne CLA 		no flags Details | Diff
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description John Arthorne CLA 2010-07-02 11:30:46 EDT 
This test has failed in the last two 3.6.x maintenance builds. See bug 51538 for details. It fails on win32, Java 6.

junit.framework.AssertionFailedError: While resuming from yieldRule, implicit
Job should only run once expected:<0> but was:<1>
at
org.eclipse.core.tests.runtime.jobs.YieldTest.testResumingThreadJobIsNotRescheduled(YieldTest.java:981)
at org.eclipse.test.EclipseTestRunner.run(EclipseTestRunner.java:376)
at org.eclipse.test.EclipseTestRunner.run(EclipseTestRunner.java:209)
at org.eclipse.test.CoreTestApplication.runTests(CoreTestApplication.java:35)
at org.eclipse.test.CoreTestApplication.run(CoreTestApplication.java:31)
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:110)
at
org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:79)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:369)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:179)
at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:619)
at org.eclipse.equinox.launcher.Main.basicRun(Main.java:574)
at org.eclipse.equinox.launcher.Main.run(Main.java:1407)
at org.eclipse.equinox.launcher.Main.main(Main.java:1383)
at org.eclipse.core.launcher.Main.main(Main.java:34)
Comment 1 John Arthorne CLA 2010-07-02 11:34:23 EDT 
Min, can you take a look at this test? We haven't changed anything since 3.6.0 but it failed twice in a row now. It could just be a bad test.
Comment 2 DJ Houghton CLA 2010-07-08 09:32:44 EDT 
Note this also failed this week in the maintenance build M20100707-1005 and the nightly build N20100707-2000.
Comment 3 John Arthorne CLA 2010-07-19 17:57:51 EDT 
This is a faulty condition in the test. It is asserting that no other jobs run during the test. However, a completely unrelated job could be run by the platform, the test framework, etc, that would cause the condition to fail. I suspect some recent change elsewhere in the platform or test infrastructure cased this to start failing. It should instead only assert that the specific jobs in the test are only run the expected number of times.
Comment 4 John Arthorne CLA 2010-07-19 17:58:27 EDT 
Created attachment 174684 [details]
Fix to the test
Comment 5 John Arthorne CLA 2010-07-19 18:00:02 EDT 
Fix released in HEAD.