maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Tibor Digana (JIRA)" <>
Subject [jira] [Commented] (SUREFIRE-1255) Surefire 2.19.1 hangs before starting test execution
Date Mon, 29 Aug 2016 08:57:20 GMT


Tibor Digana commented on SUREFIRE-1255:

If the main process is killed after specified timeout, STDIN would not
know and the CI would not be able  to perform {{mvn clean}}.


> Surefire 2.19.1 hangs before starting test execution
> ----------------------------------------------------
>                 Key: SUREFIRE-1255
>                 URL:
>             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.
> 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
> [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:

This message was sent by Atlassian JIRA

View raw message