maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kristian Rosenvold (JIRA)" <j...@codehaus.org>
Subject [jira] Commented: (SUREFIRE-707) NullPointerException in ConcurrentReporterManager on testSkipped (@Ignore on test class)
Date Thu, 03 Mar 2011 11:24:22 GMT

    [ http://jira.codehaus.org/browse/SUREFIRE-707?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=258331#action_258331
] 

Kristian Rosenvold commented on SUREFIRE-707:
---------------------------------------------

Also here I suspect forkedProcessTimeoutInSeconds set to something non-zero when this happens
?

Those runaway threads seem to indicate forkedProcessTimeoutInSeconds is not safe to use in
parallel mode at the moment. Although the issue is actually present in all the providers,
it only really has consequences in parallel.

> NullPointerException in ConcurrentReporterManager on testSkipped (@Ignore on test class)
> ----------------------------------------------------------------------------------------
>
>                 Key: SUREFIRE-707
>                 URL: http://jira.codehaus.org/browse/SUREFIRE-707
>             Project: Maven Surefire
>          Issue Type: Bug
>          Components: Junit 4.7+ (parallel) support
>    Affects Versions: 2.7.2
>         Environment: $ mvn -version
> Apache Maven 3.0.2 (r1056850; 2011-01-08 19:58:10-0500)
> Java version: 1.6.0_22, vendor: Sun Microsystems Inc.
> Java home: /usr/lib/jvm/java-6-sun-1.6.0.22/jre
> Default locale: en_US, platform encoding: UTF-8
> OS name: "linux", version: "2.6.35-25-generic", arch: "amd64", family: "unix"
>            Reporter: Mark Renouf
>
> Captured using a custom RunListener, tracing to a file:
> 2011-02-28-13:30:02.137 TEST_FAILED   - Test mechanism: null
> java.lang.NullPointerException
>         at org.apache.maven.surefire.junitcore.ConcurrentReporterManager.testSkipped(ConcurrentReporterManager.java:107)
>         at org.apache.maven.surefire.common.junit4.JUnit4RunListener.testIgnored(JUnit4RunListener.java:68)
>         at org.junit.runner.notification.RunNotifier$6.notifyListener(RunNotifier.java:130)
>         at org.junit.runner.notification.RunNotifier$SafeNotifier.run(RunNotifier.java:41)
>         at org.junit.runner.notification.RunNotifier.fireTestIgnored(RunNotifier.java:127)
>         at org.junit.internal.builders.IgnoredClassRunner.run(IgnoredClassRunner.java:19)
>         at org.junit.runners.Suite.runChild(Suite.java:128)
>         at org.junit.runners.Suite.runChild(Suite.java:24)
>         at org.junit.runners.ParentRunner$3.run(ParentRunner.java:193)
>         at org.apache.maven.surefire.junitcore.ConfigurableParallelComputer$AsynchronousRunner$1.call(ConfigurableParallelComputer.java:185)
>         at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
>         at java.util.concurrent.FutureTask.run(FutureTask.java:138)
>         at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
>         at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
>         at java.lang.Thread.run(Thread.java:662)

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message