You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Christopher Mosher (JIRA)" <ji...@codehaus.org> on 2013/04/28 06:23:52 UTC
[jira] (SUREFIRE-992) Surefire trims too much stack, with
trimStackTrace=true
Christopher Mosher created SUREFIRE-992:
-------------------------------------------
Summary: Surefire trims too much stack, with trimStackTrace=true
Key: SUREFIRE-992
URL: https://jira.codehaus.org/browse/SUREFIRE-992
Project: Maven Surefire
Issue Type: Bug
Components: Maven Surefire Plugin
Affects Versions: 2.14.1
Environment: geb, selenium, spock, groovy, mvn 3.0.5, linux
Reporter: Christopher Mosher
Priority: Minor
Attachments: mvn_stacktrace.tar.gz, typescript
With trimStackTrace=true, surefire trims too much of the stack, at least in some cases. In particular, selenium generates a particularly long and interesting stack trace, and surefire trims away all the useful information, including the stack frame of the test itself, which is the most important piece of information.
In the attached project (mvn_stacktrace.tar.gz), use "mvn test" to see the trimmed stack trace (it uses Firefox to run the test). Running with "mvn -DtrimStackTrace=false test" shows the full stack trace, including the vital line "at StackTraceTest.stackTraceTest(StackTraceTest.groovy:8)" which was trimmed during the first run.
See an attached typescript of a session showing both runs.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira