Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 338824

Summary:	testServletReadInParallel test failing on Hudson Mac slave
Product:	[Eclipse Project] Platform	Reporter:	Kim Moir <kim.moir>
Component:	User Assistance	Assignee:	platform-ua-inbox <platform-ua-inbox>
Status:	CLOSED WORKSFORME	QA Contact:
Severity:	normal
Priority:	P3	CC:	cgold
Version:	3.7
Target Milestone:	3.7 M7
Hardware:	PC
OS:	Windows XP
Whiteboard:
Bug Depends on:
Bug Blocks:	295393

Description Kim Moir

2011-03-03 10:44:51 EST

Not sure why it's failing.  Do you have any ideas?

https://hudson.eclipse.org/hudson/view/Eclipse%20and%20Equinox/job/eclipse-JUnit-mac/57/testReport/org.eclipse.ua.tests.help.webapp/ParallelServerAccessTest/testServletReadInParallel/

Failed

org.eclipse.ua.tests.help.webapp.ParallelServerAccessTest.testServletReadInParallel (from ParallelServerAccessTest)
Failing for the past 1 build (Since Unstable#57 )
Took 10 sec.
edit description
Error Message

Test did not complete within 10 seconds

Stacktrace

junit.framework.AssertionFailedError: Test did not complete within 10 seconds
	at org.eclipse.ua.tests.help.webapp.ParallelServerAccessTest.accessInParallel(ParallelServerAccessTest.java:68)
	at org.eclipse.ua.tests.help.webapp.ParallelServerAccessTest.testServletReadInParallel(ParallelServerAccessTest.java:49)
	at org.eclipse.test.EclipseTestRunner.run(EclipseTestRunner.java:416)
	at org.eclipse.test.EclipseTestRunner.run(EclipseTestRunner.java:249)
	at org.eclipse.test.UITestApplication$2.run(UITestApplication.java:197)
	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:3866)
	at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3545)
	at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2700)
	at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2664)
	at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2498)
	at org.eclipse.ui.internal.Workbench$7.run(Workbench.java:674)
	at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
	at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:667)
	at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149)
	at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:115)
	at org.eclipse.test.UITestApplication.runApplication(UITestApplication.java:140)
	at org.eclipse.test.UITestApplication.run(UITestApplication.java:62)
	at org.eclipse.test.UITestApplication.start(UITestApplication.java:212)
	at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196)
	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 Chris Goldthorpe

2011-03-03 13:26:38 EST

This test is creating 10 threads and performing 100 servlet reads on each thread and is testing for a race condition. It also has a time out of 10 seconds which is probably too short if run on a slow machine - would you characterize the Hudson Mac slave as a slow machine? If there was a race condition I would expect the test to fail in a different way but I can't completely eliminate the possibility of deadlock without being able to reproduce the failure.

Probably the best move would be to remove the timeout or make it much larger and see what happens. Does it fail consistently on this machine or is this a one off failure?

Comment 2 Chris Goldthorpe

2011-03-03 16:16:19 EST

I have increased the timeout from 10 seconds to 100. I expect that this will resolve the problem but I will wait for test results to verify this.

Comment 3 Kim Moir

2011-03-03 16:20:28 EST

The mac slave is a mac mini so I don't think it's as powerful as the current
machine we have in our build lab.  I'll run the tests again and see if the
error occurs again or is just intermittent.

Comment 4 Chris Goldthorpe

2011-04-26 13:42:12 EDT

Is the test passing now?

Comment 5 Kim Moir

2011-04-26 14:30:07 EDT

yes :-)