maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Andreas Gudian (JIRA)" <>
Subject [jira] (SUREFIRE-962) SmartStackTraceParser cannot handle manipulated stack traces gracefully
Date Sat, 23 Feb 2013 00:00:13 GMT


Andreas Gudian commented on SUREFIRE-962:

Thanks for the example! It turned out that it's not the stack trace that was the problem,
but the "display name" of the test description. Usually, it contains the test class name,
in this case it was something different.

I did a quick fix that now returns the not-so-smart localizedMessage of the exception.
> SmartStackTraceParser cannot handle manipulated stack traces gracefully
> -----------------------------------------------------------------------
>                 Key: SUREFIRE-962
>                 URL:
>             Project: Maven Surefire
>          Issue Type: Bug
>         Environment: 2.13, 2.14-SNAPSHOT
>            Reporter: Sebastian Schuth
>             Fix For: 2.14
> Following setup:
> cucumber-jvm runs specs using a JUnit Test case.
> In case of an error, surefire seems to try to be smart and parses the stack trace cucumber-jvm
has, well, somewhat manipulated. 
> As far as i can tell, {{SmartStackTraceParser}} is not able to handle manipulated stack
traces gracefully.
> This leads to following maven output:
> {code}
> [ERROR] Failed to execute goal org.apache.maven.plugins:maven-surefire-plugin:2.14-SNAPSHOT:test
(default-test) on project customer: Execution default-test of goal org.apache.maven.plugins:maven-surefire-plugin:2.14-SNAPSHOT:test
failed: There was an error in the forked process
> [ERROR] org.apache.maven.surefire.testset.TestSetFailedException: java.lang.RuntimeException:
java.lang.ClassNotFoundException: Scenario: Destinations get exchanged; nested exception is
java.lang.RuntimeException: java.lang.ClassNotFoundException: Scenario: Destinations get exchanged
> [ERROR] java.lang.RuntimeException: java.lang.ClassNotFoundException: Scenario: Destinations
get exchanged
> [ERROR] at
> [ERROR] at<init>(
> [ERROR] at org.apache.maven.surefire.common.junit4.JUnit4StackTraceWriter.smartTrimmedStackTrace(
> [ERROR] at org.apache.maven.surefire.booter.ForkingRunListener.encode(
> [ERROR] at org.apache.maven.surefire.booter.ForkingRunListener.encode(
> [ERROR] at org.apache.maven.surefire.booter.ForkingRunListener.toString(
> [ERROR] at org.apache.maven.surefire.booter.ForkingRunListener.testFailed(
> [ERROR] at org.apache.maven.surefire.common.junit4.JUnit4RunListener.testFailure(
> [ERROR] at org.junit.runner.notification.RunNotifier$4.notifyListener(
> [ERROR] at org.junit.runner.notification.RunNotifier$
> [ERROR] at org.junit.runner.notification.RunNotifier.fireTestFailures(
> [ERROR] at org.junit.runner.notification.RunNotifier.fireTestFailure(
> [ERROR] at org.junit.internal.runners.model.EachTestNotifier.addFailure(
> [ERROR] at cucumber.runtime.junit.JUnitReporter.result(
> [ERROR] at cucumber.runtime.Runtime.runStep(
> [ERROR] at cucumber.runtime.model.StepContainer.runStep(
> [ERROR] at cucumber.runtime.model.StepContainer.runSteps(
> [ERROR] at
> [ERROR] at
> [ERROR] at cucumber.runtime.junit.FeatureRunner.runChild(
> [ERROR] at cucumber.runtime.junit.FeatureRunner.runChild(
> {code}
> Version 2.12.3 can handle the manipulated stack trace.
> To be clear: i am not really sure if this is an error within surefire or if cucumber-jvm
should just keep its hands off the stack trace it produces, but the behavior of surefire changed
between 2.12 and 2.13, so this may be worth fixing.
> If you are interested in fixing this, i will happily create a project for reproducing
the error. 

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:!default.jspa
For more information on JIRA, see:


View raw message