[
https://issues.jboss.org/browse/JBIDE-11301?page=com.atlassian.jira.plugi...
]
Alexey Kazakov commented on JBIDE-11301:
----------------------------------------
Yes, I can find a stacktrace in Hudson in result page and I even can find this stacktrace
in <plugin>/<target>/surefire-reports folder (see the description of this
issue) but I can't see it in console output when I running the build *locally*.
It's very easy to reproduce:
1. Open org.jboss.tools.cdi.core.test.CDIImagesTest
2. Add the following method
{code}
public void testFoo() {
fail("You should see a stacktrace here");
}
{code}
3. mvn clean install -fae -e -P default -f
cdi/tests/org.jboss.tools.cdi.core.test/pom.xml
4. There is no stacktrace for testFoo() in console output (*that's the problem!*). But
you can find it in cdi/tests/org.jboss.tools.cdi.core.test/target/surefire-reports/*
no stacktrace when junit tests fail
-----------------------------------
Key: JBIDE-11301
URL:
https://issues.jboss.org/browse/JBIDE-11301
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: Build/Releng
Affects Versions: 3.3.0.Beta2
Reporter: Alexey Kazakov
Assignee: Mickael Istria
If I run JBT tycho build locally for trunk, for example:
mvn clean install -fae -e -P default -f cdi/tests/pom.xml
and there is some test failures then I don't see any stacktrace in console. Just a
text message from the JUnit test assert.
-Dsurefire.useFile=false does not help.
But I see the stacktrace in <target>/surefire-reports
In Beta1 branch it works fine.
I don't see stacktrace in console output in Hudson either but I'm not sure
it's a problem there.
For example
https://hudson.qa.jboss.com/hudson/view/DevStudio/view/DevStudio_Trunk/jo...
But for local builds it's very useful to see the full stacktrace in console.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see:
http://www.atlassian.com/software/jira