[ 
https://issues.apache.org/jira/browse/SUREFIRE-1946?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17465914#comment-17465914
 ] 

Tibor Digana edited comment on SUREFIRE-1946 at 12/28/21, 12:24 AM:
--------------------------------------------------------------------

Due to {{*Test mechanism*}} in the logs, it looks like an internal error in 
JUnit.
But is it really so?

{code:java}
    public static void rethrowAnyTestMechanismFailures( Result run )
        throws TestSetFailedException
    {
        for ( Failure failure : run.getFailures() )
        {
            if ( isFailureInsideJUnitItself( failure.getDescription() ) )
            {
                throw new TestSetFailedException( failure.getTestHeader() + " 
:: " + failure.getMessage(),
                                                        failure.getException() 
);
            }
        }
    }
{code}



was (Author: tibor17):
Due to {{Test mechanism}} in the logs, it looks like an internal error in JUnit.
But is it really so?

{code:java}
    public static void rethrowAnyTestMechanismFailures( Result run )
        throws TestSetFailedException
    {
        for ( Failure failure : run.getFailures() )
        {
            if ( isFailureInsideJUnitItself( failure.getDescription() ) )
            {
                throw new TestSetFailedException( failure.getTestHeader() + " 
:: " + failure.getMessage(),
                                                        failure.getException() 
);
            }
        }
    }
{code}


> Stack trace is ommited by ForkStarter.fork if forkClient.isErrorInFork
> ----------------------------------------------------------------------
>
>                 Key: SUREFIRE-1946
>                 URL: https://issues.apache.org/jira/browse/SUREFIRE-1946
>             Project: Maven Surefire
>          Issue Type: Bug
>          Components: process forking
>    Affects Versions: 3.0.0-M5
>            Reporter: Flavia Rainone
>            Priority: Major
>              Labels: waiting-for-feedback
>
> If there is an error in the fork client (forkClient.isErrorInFork), only the 
> title of the exception is shown, and without the stack trace that caused that 
> exception, it is hard to be able to figure what is causing the error.
> In my case, I'm getting a NPE, and the output shows solely:
> {code:java}
> [ERROR] Failed to execute goal 
> org.apache.maven.plugins:maven-surefire-plugin:3.0.0-M5:test (default-test) 
> on project undertow-core: There are test failures.
> [ERROR] 
> [ERROR] Please refer to 
> /home/fla/Development/projects/undertow/core/target/surefire-reports for the 
> individual test results.
> [ERROR] Please refer to dump files (if any exist) [date].dump, 
> [date]-jvmRun[N].dump and [date].dumpstream.
> [ERROR] There was an error in the forked process
> [ERROR] Test mechanism :: java.lang.NullPointerException
> [ERROR] org.apache.maven.surefire.booter.SurefireBooterForkException: There 
> was an error in the forked process
> [ERROR] Test mechanism :: java.lang.NullPointerException
> [ERROR]       at 
> org.apache.maven.plugin.surefire.booterclient.ForkStarter.fork(ForkStarter.java:733)
> [ERROR]       at 
> org.apache.maven.plugin.surefire.booterclient.ForkStarter.run(ForkStarter.java:305)
> [ERROR]       at 
> org.apache.maven.plugin.surefire.booterclient.ForkStarter.run(ForkStarter.java:265)
> [ERROR]       at 
> org.apache.maven.plugin.surefire.AbstractSurefireMojo.executeProvider(AbstractSurefireMojo.java:1314)
> [ERROR]       at 
> org.apache.maven.plugin.surefire.AbstractSurefireMojo.executeAfterPreconditionsChecked(AbstractSurefireMojo.java:1159)
> [ERROR]       at 
> org.apache.maven.plugin.surefire.AbstractSurefireMojo.execute(AbstractSurefireMojo.java:932)
> [ERROR]       at 
> org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:137)
> [ERROR]       at 
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:210)
> [ERROR]       at 
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:156)
> [ERROR]       at 
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:148)
> [ERROR]       at 
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:117)
> [ERROR]       at 
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:81)
> [ERROR]       at 
> org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.java:56)
> [ERROR]       at 
> org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:128)
> [ERROR]       at 
> org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:305)
> [ERROR]       at 
> org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:192)
> [ERROR]       at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:105)
> [ERROR]       at org.apache.maven.cli.MavenCli.execute(MavenCli.java:957)
> [ERROR]       at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:289)
> [ERROR]       at org.apache.maven.cli.MavenCli.main(MavenCli.java:193)
> [ERROR]       at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> [ERROR]       at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> [ERROR]       at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> [ERROR]       at java.lang.reflect.Method.invoke(Method.java:498)
> [ERROR]       at 
> org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:282)
> [ERROR]       at 
> org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:225)
> [ERROR]       at 
> org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:406)
> [ERROR]       at 
> org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:347)
> [ERROR] 
> [ERROR] -> [Help 1]
> [ERROR] 
> {code}



--
This message was sent by Atlassian Jira
(v8.20.1#820001)

Reply via email to