Hi Mickael,
I understand we are going to address all test problems eventually. Is there way to let the build run, however, before the test problems are fixed. It looks that maven.test.error.ignore=true and maven.test.failure.ignore=true doesn't work. Are there other switches which can help?
Best Regards
Samuel Wu
Mickael Istria ---02/09/2015 05:11:40 PM---On 02/09/2015 11:00 PM, Samuel Wu wrote: >
From: Mickael Istria <mistria@xxxxxxxxxx>
To: cbi-dev@xxxxxxxxxxx
Date: 02/09/2015 05:11 PM
Subject: Re: [cbi-dev] Mark a build as failed when the compile failed
Sent by: cbi-dev-bounces@xxxxxxxxxxx
On 02/09/2015 11:00 PM, Samuel Wu wrote:
Hi Mickael,
Unfortunately when I changed the Fail Mode to At_End, the build failed.
At least now, you know they're failing. It's better ;)
Fir this one, you'll need to have a look at the details in the log for this specific bundles. Could be a ClassNotFound, a Timeout, a configuration error...
[ERROR] Failed to execute goal org.eclipse.tycho:tycho-surefire-plugin:0.20.0:test (default-test) on project org.eclipse.wst.wsi.tests: No tests found. -> [Help 1]
This bundle builds as a nested jar ( http://git.eclipse.org/c/webservices/webtools.webservices.git/tree/tests/org.eclipse.wst.wsi.tests/build.properties#n2 ) and Tycho doesn't like it. So you should just build it as a regular bundle, and if a subset of it has to be a nested jar, extract it in its dedicated source folder and build only this source folder as a nested jar. Test classes have to be at the root of the bundle.
--
Mickael Istria
Eclipse developer at JBoss, by Red Hat
My blog - My Tweets_______________________________________________
cbi-dev mailing list
cbi-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/cbi-dev
|