[jbosstools-dev] Tests failures

[Alexey Kazakov]

I'm talking about local builds. Not hudson.
And I do run it with the -e flag.
For example:
mvn clean install -fae -e -P default -f cdi/tests/pom.xml
I will take a look at .log file in target folder but anyway it would be 
much more useful to get a stacktrace in console as we had before.

On 03/07/2012 09:26 PM, Nick Boldt wrote:
> Builds should be running with the -e flag so that when they fail you 
> get a stacktrace. Failing that, check the console .log for the eclipse 
> instance running the test, for example:
>
> https://hudson.qa.jboss.com/hudson/view/DevStudio/view/DevStudio_Trunk/job/jbosstools-3.3_trunk.component--jsf/ws/sources/tests/org.jboss.tools.jsf.vpe.richfaces.test/target/work/data/.metadata/.log 
>
>
> (or more generically...)
>
> https://hudson.qa.jboss.com/hudson/job/{jobname}/ws/sources/tests/{testclass}/target/work/data/.metadata/.log 
>
>
> Going forward, we plan to archive these log files so they persist 
> longer in Jenkins between builds. See 
> https://issues.jboss.org/browse/JBDS-2031.
>
> N
>
> On 03/07/2012 08:33 PM, Alexey Kazakov wrote:
>> Hi Nick,
>> There is no stacktrace anymore when tests are failed in tycho build.
>> Just a short message like: Test failure: testNNN(org.jboss.NNN): some
>> test message.
>> Stacktrace was very useful there. Can we get it back somehow?
>> _______________________________________________
>> jbosstools-dev mailing list
>> jbosstools-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/jbosstools-dev
>