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

Tibor Digana commented on SUREFIRE-1255:
----------------------------------------

The snapshot version is deployed these days very often, see our Jenkins build
https://builds.apache.org/job/maven-surefire/

I want to minize the tries in Travis, and of course if it is not free service 
we should try only few times.
For you it would be the most simple solution to specify version of surefire via 
system property in CI without modifying project in GitHub.

I want to add logs tracking the commands flow between Maven process and 
Surefire forked processes. I think some command is lost or some internal error 
broke the mechanism dispatching the commands or the stream is somehow corrupted.
I will let you know after I have prepared all logs in our snapshot version for 
making the analysis.

> Surefire 2.19.1 hangs before starting test execution
> ----------------------------------------------------
>
>                 Key: SUREFIRE-1255
>                 URL: https://issues.apache.org/jira/browse/SUREFIRE-1255
>             Project: Maven Surefire
>          Issue Type: Bug
>          Components: Maven Surefire Plugin, process forking
>    Affects Versions: 2.19.1
>            Reporter: Maximilian Michels
>            Assignee: Tibor Digana
>            Priority: Critical
>
> Seeing the same error as SUREFIRE-1193 in Apache Flink builds after upgrading 
> from 2.18.1 to 2.19.1. No errors, builds just gets stuck at the beginning of 
> tests with no log output from the test itself, e.g. 
> https://s3.amazonaws.com/archive.travis-ci.org/jobs/137118454/log.txt
> After a couple of minutes Surefire reports 
> {noformat}
> [ERROR] Failed to execute goal 
> org.apache.maven.plugins:maven-surefire-plugin:2.19.1:test 
> (integration-tests) on project flink-scala-shell_2.10: ExecutionException The 
> forked VM terminated without properly saying goodbye. VM crash or System.exit 
> called?
> [ERROR] Command was /bin/sh -c cd 
> /home/travis/build/mxm/flink/flink-scala-shell/target && 
> /usr/lib/jvm/java-8-oracle/jre/bin/java -Xms256m -Xmx800m -Dmvn.forkNumber=1 
> -XX:-UseGCOverheadLimit -jar 
> /home/travis/build/mxm/flink/flink-scala-shell/target/surefire/surefirebooter372520169616801479.jar
>  
> /home/travis/build/mxm/flink/flink-scala-shell/target/surefire/surefire8229439069544382018tmp
>  
> /home/travis/build/mxm/flink/flink-scala-shell/target/surefire/surefire_26373613144387982724tmp
> [ERROR] -> [Help 1]
> {noformat}
> We have a a couple of test classes that suffer from this problem. Tests don't 
> read from STDIN or replace it. Switching back to 2.18.1 eliminates the 
> problem (Ran over 100 builds). It seems to be a race condition because it 
> only occurs every once in a while, i.e. ~ 2 out of 10 builds on Travis. I 
> haven't been able to reproduce the problem locally.
> More logs: 
> https://s3.amazonaws.com/flink-logs-us/travis-artifacts/mxm/flink/849/849.1.tar.gz



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

Reply via email to