Community
Participate
Working Groups
The test case IJobManagerTest.testJobFamilyWakeUp has a race condition that causes the test to fail incorrectly. Here is the current code: if (family1[i].getState() == Job.RUNNING) runningCount++; else assertState("7.1." + i, family1[i], Job.WAITING); The intent is to verify that the job is either waiting or running. However, there are two calls to job.getState(). If the job is still waiting when getState() is called the first time, we enter the else block. At this point the job starts running, and the assertion fails because it expects waiting. We can see from the failure message that this is what happened: 7.1.0: expected state: WAITING actual state: RUNNING It is perfectly valid that the job is running here, we just have a badly written test.
http://git.eclipse.org/c/platform/eclipse.platform.runtime.git/commit/?id=deb0fa63c65ca4a42bad2b565cbeead62ef85944
Verified in I20130430-0031.
Looks like this was not all of it. Failed again in I20130511-1500: http://download.eclipse.org/eclipse/downloads/drops4/I20130511-1500/testresults/html/org.eclipse.core.tests.runtime_macosx.cocoa.x86_5.0.html
Difference occurrence of the same bad pattern. Fixed: http://git.eclipse.org/c/platform/eclipse.platform.runtime.git/commit/?id=4982b24a410823d36e2a49fcad28d68d8e55a7c2
Verified in I20130513-2000.