[
https://jira.codehaus.org/browse/SUREFIRE-991?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=326282#comment-326282
]
Matthias Fraass commented on SUREFIRE-991:
------------------------------------------
Kristian, please roll out 2.15 soon as we have to use a 2.15-SNAPSHOT now and
the maven-release-plugin forbids using SNAPSHOTS for official releases!
> NPE when all tests are done with failsafe (parallel=classes) and cucumber-jvm
> -----------------------------------------------------------------------------
>
> Key: SUREFIRE-991
> URL: https://jira.codehaus.org/browse/SUREFIRE-991
> Project: Maven Surefire
> Issue Type: Bug
> Components: Junit 4.7+ (parallel) support, Maven Failsafe Plugin
> Affects Versions: 2.14.1
> Reporter: Maxime Mériouma-Caron
> Assignee: Andreas Gudian
> Priority: Blocker
> Fix For: 2.15
>
>
> I've made a concurrent setup to run my cucumbers/selenium tests with failsafe
> with the option parallel set to classes. When all my tests are done and
> passed (no failure, no error), I get the following stacktrace :
> org.apache.maven.surefire.testset.TestSetFailedException:
> java.lang.NullPointerException; nested exception is
> java.lang.NullPointerException: null
> java.lang.NullPointerException
> at
> org.apache.maven.surefire.junitcore.ConcurrentRunListener.testSucceeded(ConcurrentRunListener.java:138)
> at
> org.apache.maven.surefire.common.junit4.JUnit4RunListener.testFinished(JUnit4RunListener.java:145)
> at
> org.junit.runner.notification.RunNotifier$7.notifyListener(RunNotifier.java:191)
> at
> org.junit.runner.notification.RunNotifier$SafeNotifier.run(RunNotifier.java:61)
> at
> org.junit.runner.notification.RunNotifier.fireTestFinished(RunNotifier.java:188)
> at
> org.junit.internal.runners.model.EachTestNotifier.fireTestFinished(EachTestNotifier.java:39)
> at
> cucumber.runtime.junit.JUnitReporter.finishExecutionUnit(JUnitReporter.java:55)
> at
> cucumber.runtime.junit.ExecutionUnitRunner.run(ExecutionUnitRunner.java:84)
> at cucumber.runtime.junit.FeatureRunner.runChild(FeatureRunner.java:63)
> at cucumber.runtime.junit.FeatureRunner.runChild(FeatureRunner.java:18)
> at org.junit.runners.ParentRunner$3.run(ParentRunner.java:238)
> at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:63)
> at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:236)
> at org.junit.runners.ParentRunner.access$000(ParentRunner.java:53)
> at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:229)
> at org.junit.runners.ParentRunner.run(ParentRunner.java:309)
> at cucumber.runtime.junit.FeatureRunner.run(FeatureRunner.java:70)
> at cucumber.api.junit.Cucumber.runChild(Cucumber.java:77)
> at cucumber.api.junit.Cucumber.runChild(Cucumber.java:37)
> at org.junit.runners.ParentRunner$3.run(ParentRunner.java:238)
> at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:63)
> at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:236)
> at org.junit.runners.ParentRunner.access$000(ParentRunner.java:53)
> at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:229)
> at org.junit.runners.ParentRunner.run(ParentRunner.java:309)
> at cucumber.api.junit.Cucumber.run(Cucumber.java:82)
> which makes my maven build fail.
--
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
