Bugzilla – Full Text Bug Listing
| Summary: | Test failures in N20091122-2000 | ||
|---|---|---|---|
| Product: | [Eclipse Project] Platform | Reporter: | Szymon Brandys <Szymon.Brandys> |
| Component: | Runtime | Assignee: | John Arthorne <john.arthorne> |
| Status: | RESOLVED FIXED | QA Contact: | |
| Severity: | major | ||
| Priority: | P3 | CC: | john.arthorne, markus.kell.r, min123, tomasz.zarna |
| Version: | 3.6 | ||
| Target Milestone: | 3.6 M4 | ||
| Hardware: | PC | ||
| OS: | Mac OS X - Carbon (unsup.) | ||
| URL: | http://fullmoon.ottawa.ibm.com/downloads/drops/N20091122-2000/testresults/html/org.eclipse.team.tests.cvs.core_macosx.cocoa.x86_5.0.html | ||
| Whiteboard: | |||
| Bug Depends on: | 283449 | ||
| Bug Blocks: | |||
|
Description
Szymon Brandys
The tests failed in N20091120-2000 as well, but passed in N20091121-2000. Moreover, they also passed locally on our Mac. We haven't touched that code recently so all results should be the same (pass). I guess this is an intermittent failure, which does not indicate a problem with the build. I keep my fingers crossed for still running tests for N20091123-2000. Tests for N20091123-2000 failed, I'm re-running them locally for the latest N-build. John, could these problems be related to your latest changes in core.job? First time we re-run the tests (all CVS tests) they failed locally. So we checked out o.e.core.jobs to find out if this is not caused by a fix recently committed to that project (Szymon's suspicion). As expected, tests passed (with o.e.jobs v20090921), so we switched to HEAD and ran them again. This time they... passed. This is strange. (In reply to comment #4) > First time we re-run the tests (all CVS tests) they failed locally. So we > checked out o.e.core.jobs to find out if this is not caused by a fix recently > committed to that project (Szymon's suspicion). As expected, tests passed (with > o.e.jobs v20090921), so we switched to HEAD and ran them again. This time > they... passed. This is strange. That just suggests that the failure is intermittent. If you can reproduce the problem with the old core.jobs that would rule out that as the cause. If the tests run several times in a row on old core.jobs without failure, but frequently fail on new core.jobs, that may be the cause of the failure. I am also noticing that this test is timing out on all platforms (windows, linux, and mac), starting in N20091120-2000: java-test: [echo] Running org.eclipse.team.tests.ccvs.core.AllTests. Result file: C:\buildtest\N20091120-2000\eclipse-testing/results/win32.win32.x86/org.eclipse.team.tests.ccvs.core.AllTests.xml. [java] Timeout: killed the sub-process [java] at org.apache.tools.ant.taskdefs.Java.fork(Java.java:787) This doesn't seem to show up as a test failure though. Notice that only 48 tests ran on windows and linux starting in N20091120, rather than 236 tests before that. I think I have found out the source of the timeouts. See bug 296056. I'm still trying to see if the beginRule error is related. > I am also noticing that this test is timing out on all platforms (windows, > linux, and mac), starting in N20091120-2000: [..] > This doesn't seem to show up as a test failure though. See bug 210792 for reporting when a test timed out. The same failure happened in the JDT text tests in I20091124-0800, so this must be related to the core.jobs changes. Attempted to beginRule: R/, does not match outer scope rule: P/TestProject1 java.lang.IllegalArgumentException: Attempted to beginRule: R/, does not match outer scope rule: P/TestProject1 at org.eclipse.core.runtime.Assert.isLegal(Assert.java:63) at org.eclipse.core.internal.jobs.ThreadJob.illegalPush(ThreadJob.java:132) at org.eclipse.core.internal.jobs.ThreadJob.push(ThreadJob.java:351) at org.eclipse.core.internal.jobs.ImplicitJobs.begin(ImplicitJobs.java:68) at org.eclipse.core.internal.jobs.JobManager.beginRule(JobManager.java:260) at org.eclipse.core.internal.resources.WorkManager.checkIn(WorkManager.java:117) at org.eclipse.core.internal.resources.Workspace.prepareOperation(Workspace.java:1796) at org.eclipse.core.internal.resources.Project.setDescription(Project.java:1054) at org.eclipse.core.internal.resources.Project.setDescription(Project.java:1108) at org.eclipse.jdt.testplugin.JavaProjectHelper.addNatureToProject(JavaProjectHelper.java:741) at org.eclipse.jdt.testplugin.JavaProjectHelper.createJavaProject(JavaProjectHelper.java:146) at org.eclipse.jdt.text.tests.contentassist.CodeCompletionTest.setUp(CodeCompletionTest.java:102) at org.eclipse.test.EclipseTestRunner.run(EclipseTestRunner.java:354) at org.eclipse.test.EclipseTestRunner.run(EclipseTestRunner.java:206) at org.eclipse.test.UITestApplication$3.run(UITestApplication.java:195) at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35) at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:134) at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:3906) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3527) at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2404) at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2368) at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2220) at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:500) at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332) at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:493) at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149) at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:113) at org.eclipse.test.UITestApplication.runApplication(UITestApplication.java:138) at org.eclipse.test.UITestApplication.run(UITestApplication.java:60) at org.eclipse.test.UITestApplication.start(UITestApplication.java:210) at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:194) 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:367) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:179) at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:611) at org.eclipse.equinox.launcher.Main.basicRun(Main.java:566) at org.eclipse.equinox.launcher.Main.run(Main.java:1363) at org.eclipse.equinox.launcher.Main.main(Main.java:1339) at org.eclipse.core.launcher.Main.main(Main.java:34) I have reverted the change that seems to be causing this failure (see bug 283449). I will leave this open for another day to confirm that the problem is resolved. Verified tests all complete and pass in N20091125-2000. |