maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Abel Salgado Romero (JIRA)" <>
Subject [jira] [Commented] (SUREFIRE-1255) Surefire 2.19.1 hangs before starting test execution
Date Wed, 02 May 2018 06:15:00 GMT


Abel Salgado Romero commented on SUREFIRE-1255:

I already run some isolation back when we found it doing a general upgrade:
If you want to reproduce it, just download the project from the repo,
upgrade the surefire version
and run the tests.
I honestly don't discard the issue is caused by some combination of factors, but so far this
is the only lead I found :%.

Note: the first test starts an embedded server and that can be missleading, add an {{@Ignore}}
if you prefer to see the issue with a normal test.

> 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