Bug 353482 - [test] "The operation took too long" errors in recent builds
Summary: [test] "The operation took too long" errors in recent builds
Status: RESOLVED INVALID
Alias: None
Product: Orion (Archived)
Classification: ECD
Component: Git (show other bugs)
Version: 0.2   Edit
Hardware: PC Windows XP
: P3 normal (vote)
Target Milestone: 0.3   Edit
Assignee: Project Inbox CLA
QA Contact:
URL: http://download.eclipse.org/orion/dro...
Whiteboard:
Keywords: test
Depends on:
Blocks:
 
Reported: 2011-08-01 05:28 EDT by Tomasz Zarna CLA
Modified: 2011-08-23 12:33 EDT (History)
2 users (show)

See Also:

Attachments
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 Tomasz Zarna CLA 2011-08-01 05:28:21 EDT 
Starting from I201107026-0200 we're observing errors in recent builds. They all fail with "The operation took too long" message. It's usually 1 to 3 errors per build, random tests.

Stack trace from the latest build:

testGetSingleConfigEntry

The operation took too long 

java.lang.AssertionError: The operation took too long
at org.eclipse.orion.server.tests.servlets.git.GitTest.waitForTaskCompletion(GitTest.java:239)
at org.eclipse.orion.server.tests.servlets.git.GitTest.clone(GitTest.java:320)
at org.eclipse.orion.server.tests.servlets.git.GitTest.clone(GitTest.java:381)
at org.eclipse.orion.server.tests.servlets.git.GitConfigTest.testGetSingleConfigEntry(GitConfigTest.java:304)
at org.eclipse.test.EclipseTestRunner.run(EclipseTestRunner.java:416)
at org.eclipse.test.EclipseTestRunner.run(EclipseTestRunner.java:249)
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:110)
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:79)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:344)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:179)
at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:622)
at org.eclipse.equinox.launcher.Main.basicRun(Main.java:577)
at org.eclipse.equinox.launcher.Main.run(Main.java:1410)
at org.eclipse.equinox.launcher.Main.main(Main.java:1386)
at org.eclipse.core.launcher.Main.main(Main.java:34)
Comment 1 John Arthorne CLA 2011-08-08 13:56:44 EDT 
Can you reproduce this locally or is it only on the test machine?
Comment 2 Tomasz Zarna CLA 2011-08-08 14:02:58 EDT 
I have never seen it on my local machine.
Comment 3 Tomasz Zarna CLA 2011-08-23 12:33:28 EDT 
Haven't seen it since the bug was opened. Must have been an intermittent issue. Marking as INVALID.