Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
[wtp-releng] Re: [wtp-dev] WTP 3.2.0 I-Build failure

Beats me, but my guess is this is the "mixed JUnit" requirements coming back to haunt us. I think some people still specify a "max" of 4.0.

My first thought was this was from moving up to the 0414 version of the platform, instead of 0413 ... but, on another, local, test machine, the 0414 build worked fine.

There could have been some other changes (e.g. Orbit pre-reqs) but, more likely, I removed some old stuff from our "releng tests feature" ... things we didn't use, were redundant, etc.

So ... mostly guessing ... some of the old stuff might have been forcing an early load of JUnit 3.8, and all would proceed fine .... and now, without the old stuff, some plugin loads 4.x version, but others load 3.x and chaos ensues.

But to be systematic about it, I'm going to revert "prereqs" to where there were in the last successful build, assume that still fails, will add back the old stuff (just to experiment). In parallel I'll look to see to still specifies a max Junit of 4.0, if anyone.

BTW, Shane, I think "wtp-releng" is better for these sort of day-to-day, week-to-week mostly-committers-only issues ... and wtp-dev better for wider questions or announcements to adopters (as well as committers).

Thanks for bringing this test failure to my attention.

From: shane clarke <shane_clarke@xxxxxxxxxxx>
To: <wtp-dev@xxxxxxxxxxx>
Date: 04/17/2010 06:27 PM
Subject: [wtp-dev] WTP 3.2.0 I-Build failure
Sent by: wtp-dev-bounces@xxxxxxxxxxx

Nearly all of the test suites in the last build :

are throwing the following kind of error:

[TEST_SUITE] incompatible with junit.framework.Test
java.lang.ClassCastException: [TEST_SUITE] incompatible with junit.framework.Test
at org.eclipse.test.EclipseTestRunner.getTest(
at org.eclipse.test.EclipseTestRunner.<init>(
at org.eclipse.test.UITestApplication$
at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(
at org.eclipse.swt.widgets.Display.runAsyncMessages(
at org.eclipse.swt.widgets.Display.readAndDispatch(
at org.eclipse.ui.internal.Workbench.runEventLoop(
at org.eclipse.ui.internal.Workbench.runUI(
at org.eclipse.ui.internal.Workbench.access$4(
at org.eclipse.ui.internal.Workbench$
at org.eclipse.core.databinding.observable.Realm.runWithDefault(
at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(
at org.eclipse.ui.PlatformUI.createAndRunWorkbench(
at org.eclipse.ui.internal.ide.application.IDEApplication.start(
at org.eclipse.test.UITestApplication.runApplication(
at org.eclipse.test.UITestApplication.start(
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(
at org.eclipse.equinox.launcher.Main.invokeFramework(
at org.eclipse.equinox.launcher.Main.basicRun(
at org.eclipse.equinox.launcher.Main.main(

I've been looking through the logs but i'm not sure what's caused this to happen.


Hotmail: Free, trusted and rich email service. Get it now._______________________________________________
wtp-dev mailing list

Back to the top