Bug 332044

Comment 1 Tomasz Zarna 2010-12-14 06:20:35 EST

Could that be related to the exception I get when I try to run the tests:

Failed to invoke suite(): java.lang.Error: Unresolved compilation problem: 

java.lang.reflect.InvocationTargetException
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:48)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:37)
	at java.lang.reflect.Method.invoke(Method.java:600)
	at org.eclipse.jdt.internal.junit.runner.junit3.JUnit3TestLoader.getTest(JUnit3TestLoader.java:108)
	at org.eclipse.jdt.internal.junit.runner.junit3.JUnit3TestLoader.loadTests(JUnit3TestLoader.java:59)
	at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:452)
	at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:683)
	at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.run(RemoteTestRunner.java:390)
	at org.eclipse.pde.internal.junit.runtime.RemotePluginTestRunner.main(RemotePluginTestRunner.java:62)
	at org.eclipse.pde.internal.junit.runtime.UITestApplication$1.run(UITestApplication.java:116)
	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:4059)
	at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3678)
	at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2640)
	at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2604)
	at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2438)
	at org.eclipse.ui.internal.Workbench$7.run(Workbench.java:671)
	at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
	at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:664)
	at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149)
	at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:115)
	at org.eclipse.pde.internal.junit.runtime.UITestApplication.start(UITestApplication.java:47)
	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:369)
	at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:179)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:48)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:37)
	at java.lang.reflect.Method.invoke(Method.java:600)
	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)
Caused by: java.lang.Error: Unresolved compilation problem: 

	at org.eclipse.team.tests.ccvs.ui.benchmark.WorkflowTests.suite(WorkflowTests.java:57)
	at org.eclipse.team.tests.ccvs.ui.benchmark.AllBenchmarkTests.suite(AllBenchmarkTests.java:30)
	... 37 more

Kim can do you see anything like that on the server?
	
After I added org.eclipse.core.filesystem to the MANIFEST.MF tests run fine, at least locally.

Comment 2 Tomasz Zarna 2010-12-14 10:42:20 EST

I think you can ignore the above, it's not the case. I took a look at the performance logs, here are my findings:
* there was an exception running the tests for N20101211-2000: http://fullmoon.ottawa.ibm.com/downloads/drops/N20101211-2000/performance/html/org.eclipse.team.tests.cvs.core_win32perf1.html
* no such exception for N20101204-2000 : http://fullmoon.ottawa.ibm.com/downloads/drops/N20101204-2000/performance/performance.php, but the results were not listed in the "Detailed performance data grouped by scenario prefix" section
* I20101208-1300 and I20101207-2000 look good
* last 4 m-builds seem to be fine, except for the fact that for M20101201-0800 and M20101210-0800 the results were not listed in the "Detailed performance data grouped by scenario prefix" section and there was a DNF for org.eclipse.team.tests.cvs.core_linuxgtkperf1 in M20101124-0800

Comment 3 Tomasz Zarna 2010-12-15 05:56:36 EST

The tests have run for the latest I20101214-0800, but I'm confirming Satyam's words: something happened to baseline measurement. The last one took place on 201009171800 (for I-builds) and on 20100920-1800 (for M-builds).

Kim is there anything the Team team can do about it?

Comment 4 Kim Moir 2010-12-15 08:17:39 EST

Let me look at the machines.  The artifacts from the baselines on Monday should be there, the ones from last Friday would have been deleted.

Comment 5 Kim Moir 2010-12-15 16:41:55 EST

In the 3.5.x stream it looks like they are still connecting to the old repository.

Comment 6 Kim Moir 2010-12-16 10:38:19 EST

This has been fixed and I've started another perf_35x stream baseline run.

Comment 7 Tomasz Zarna 2010-12-16 10:41:18 EST

Thanks Kim!

Comment 8 Kim Moir 2010-12-21 13:43:01 EST

Verified in last night's baseline run.