maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Tibor Digana (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (SUREFIRE-1374) std/in stream corrupted error
Date Mon, 29 May 2017 01:20:04 GMT

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

Tibor Digana commented on SUREFIRE-1374:
----------------------------------------

[~matteor]
Can you produce effective POM and send it to me? I want to know if the POM is mixing old version
of surefire and surefire providers.
Against 2.19.1 there was not any significant changes.
Does it happen always?
Are you able to download our sources and put {{System.out.println(. . . )}} in class {{MasterProcessCommand}},
install it to local maven repo and use version {{2.21-SNAPSHOT}} in you project? In that class
you will see two methods {{readInt()}} and {{is.readFully( buffer )}}. Log their values to
the console like a stream of bytes.
This would help. Additionally log this condition which should never happen {{if ( command
== null )}}.

> std/in stream corrupted error
> -----------------------------
>
>                 Key: SUREFIRE-1374
>                 URL: https://issues.apache.org/jira/browse/SUREFIRE-1374
>             Project: Maven Surefire
>          Issue Type: Bug
>          Components: Maven Surefire Plugin
>    Affects Versions: 2.20
>            Reporter: matteo rulli
>            Assignee: Tibor Digana
>
> We bumbed surefire version to 2.20 (from 2.19.1) and our tests started generating this
kind of errors:
> {code}
> # Created on 2017-05-26T10:24:04.032
> [SUREFIRE] std/in stream corrupted
> java.io.IOException: Command BYE_ACK unexpectedly read Void data with length 4.
> 	at org.apache.maven.surefire.booter.MasterProcessCommand.decode(MasterProcessCommand.java:130)
> 	at org.apache.maven.surefire.booter.CommandReader$CommandRunnable.run(CommandReader.java:386)
> 	at java.lang.Thread.run(Thread.java:745)
> {code}
> Related stacktrace:
> {code}
> [ERROR] Error occurred in starting fork, check output in log
> [ERROR] org.apache.maven.surefire.booter.SurefireBooterForkException: Error occurred
in starting fork, check output in log
> [ERROR] 	at org.apache.maven.plugin.surefire.booterclient.ForkStarter.fork(ForkStarter.java:634)
> [ERROR] 	at org.apache.maven.plugin.surefire.booterclient.ForkStarter.fork(ForkStarter.java:533)
> [ERROR] 	at org.apache.maven.plugin.surefire.booterclient.ForkStarter.run(ForkStarter.java:279)
> [ERROR] 	at org.apache.maven.plugin.surefire.booterclient.ForkStarter.run(ForkStarter.java:243)
> [ERROR] 	at org.apache.maven.plugin.surefire.AbstractSurefireMojo.executeProvider(AbstractSurefireMojo.java:1077)
> [ERROR] 	at org.apache.maven.plugin.surefire.AbstractSurefireMojo.executeAfterPreconditionsChecked(AbstractSurefireMojo.java:907)
> [ERROR] 	at org.apache.maven.plugin.surefire.AbstractSurefireMojo.execute(AbstractSurefireMojo.java:785)
> [ERROR] 	at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:134)
> [ERROR] 	at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:208)
> [ERROR] 	at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:154)
> [ERROR] 	at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:146)
> [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:51)
> [ERROR] 	at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:128)
> [ERROR] 	at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:309)
> [ERROR] 	at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:194)
> [ERROR] 	at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:107)
> [ERROR] 	at org.apache.maven.cli.MavenCli.execute(MavenCli.java:993)
> [ERROR] 	at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:345)
> [ERROR] 	at org.apache.maven.cli.MavenCli.main(MavenCli.java:191)
> [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:289)
> [ERROR] 	at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229)
> [ERROR] 	at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:415)
> [ERROR] 	at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:356)
> [
> {code}
> Everything worked fine with 2.19.1.
> Environment: macOS sierra, java version "1.8.0_74", Apache Maven 3.5.0  



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Mime
View raw message