Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [cbi-dev] Mark a build as failed when the compile failed

>I think these settings prevent even trying to compile the tests, much less run them. 

tests will be compiled, but not executed.

maybe 'mvn --fail-at-end' is what you want.

Regards,
Jan


From: cbi-dev-bounces@xxxxxxxxxxx [mailto:cbi-dev-bounces@xxxxxxxxxxx] On Behalf Of David M Williams
Sent: Dienstag, 10. Februar 2015 02:54
To: Common-build Developers discussion
Subject: Re: [cbi-dev] Mark a build as failed when the compile failed

-DskipTests=true 


and depending on your version of Tycho, might have to also specify 
-Dmaven.test.skip=true 

I think it was 0.21 that Tycho implemented an enhancement that "skipTests" would trump "maven.test.skip". Previously there were some hard to predict interactions depending if both were set but to different vales). 

I think these settings prevent even trying to compile the tests, much less run them. 

HTH 




From:        Samuel Wu <samuelwu@xxxxxxxxxx> 
To:        Common-build Developers discussion <cbi-dev@xxxxxxxxxxx>, 
Date:        02/09/2015 05:22 PM 
Subject:        Re: [cbi-dev] Mark a build as failed when the compile failed 
Sent by:        cbi-dev-bounces@xxxxxxxxxxx 
________________________________________



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 ;) 

https://hudson.eclipse.org/webtools/job/WTP-R3_7_Integration/310/
https://hudson.eclipse.org/webtools/job/WTP-R3_6_3_Maintenance/160/
It looks that the problem was caused by test.
[ERROR] Failed to execute goal org.eclipse.tycho:tycho-surefire-plugin:0.20.0:test (default-test) on project org.eclipse.jst.server.core.tests: An unexpected error occured (return code 143). See log for details. -> [Help 1] 

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_______________________________________________
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 


Back to the top