maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Thorsten Meinl (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (SUREFIRE-1197) Surefire 2.19 breaks tests under Windows due to fork problem
Date Sun, 29 Nov 2015 12:15:11 GMT

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

Thorsten Meinl commented on SUREFIRE-1197:
------------------------------------------

After renaming all jar files from your archive that have a timestamp in their names to "SNAPSHOT"
I finally got it to work. However, the only file that is created is a "surefire-finished1.1728077946.txt"
with the only content "finished normally". The fork error still occurs.


> Surefire 2.19 breaks tests under Windows due to fork problem
> ------------------------------------------------------------
>
>                 Key: SUREFIRE-1197
>                 URL: https://issues.apache.org/jira/browse/SUREFIRE-1197
>             Project: Maven Surefire
>          Issue Type: Bug
>          Components: process forking
>    Affects Versions: 2.19
>         Environment: Windows 7
>            Reporter: Thorsten Meinl
>            Assignee: Tibor Digana
>
> After switching from Surefire 2.18.1 to 2.19 our tests under Windows have stopped working
(Linux and Mac are still running fine). The only error message is
> Failed to execute goal org.apache.maven.plugins:maven-surefire-plugin:2.19:test (default-test)
on project server.ejb: Error occurred in starting fork, check output in log -> [Help 1]
> (Full stacktrace below).
> Is checked the log and even enabled full debug messages but there is not indication whatsoever
what the problem can be. Given that everything worked perfectly fine until we switched to
2.19 this seems to be a bug in this version. I'm happy to provide further details if you tell
me what you need and how I can acquire it.
> =======================
> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal org.apache.maven.plugins:maven-surefire-plugin:2.19:test
(default-test) on project server.ejb: Error occurred in starting fork, check output in log
> 	at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:212)
> 	at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
> 	at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
> 	at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:116)
> 	at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:80)
> 	at org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.java:51)
> 	at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:120)
> 	at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:355)
> 	at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:155)
> 	at org.apache.maven.cli.MavenCli.execute(MavenCli.java:584)
> 	at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:216)
> 	at org.apache.maven.cli.MavenCli.main(MavenCli.java:160)
> 	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> 	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:95)
> 	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:55)
> 	at java.lang.reflect.Method.invoke(Method.java:507)
> 	at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:289)
> 	at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229)
> 	at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:415)
> 	at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:356)
> Caused by: org.apache.maven.plugin.MojoFailureException: Error occurred in starting fork,
check output in log
> 	at org.apache.maven.plugin.surefire.SurefirePlugin.assertNoException(SurefirePlugin.java:326)
> 	at org.apache.maven.plugin.surefire.SurefirePlugin.handleSummary(SurefirePlugin.java:316)
> 	at org.apache.maven.plugin.surefire.AbstractSurefireMojo.executeAfterPreconditionsChecked(AbstractSurefireMojo.java:880)
> 	at org.apache.maven.plugin.surefire.AbstractSurefireMojo.execute(AbstractSurefireMojo.java:739)
> 	at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:132)
> 	at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:208)
> 	... 19 more
> Caused by: org.apache.maven.surefire.booter.SurefireBooterForkException: Error occurred
in starting fork, check output in log
> 	at org.apache.maven.plugin.surefire.booterclient.ForkStarter.fork(ForkStarter.java:559)
> 	at org.apache.maven.plugin.surefire.booterclient.ForkStarter.fork(ForkStarter.java:461)
> 	at org.apache.maven.plugin.surefire.booterclient.ForkStarter.run(ForkStarter.java:229)
> 	at org.apache.maven.plugin.surefire.booterclient.ForkStarter.run(ForkStarter.java:201)
> 	at org.apache.maven.plugin.surefire.AbstractSurefireMojo.executeProvider(AbstractSurefireMojo.java:1014)
> 	at org.apache.maven.plugin.surefire.AbstractSurefireMojo.executeAfterPreconditionsChecked(AbstractSurefireMojo.java:850)
> 	... 22 more



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message