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

Maximilian Michels commented on SUREFIRE-1255:
----------------------------------------------

[~tibor17] Thanks for getting back to me.

{quote}
How many test classes left not been started?
{quote}
It seems like the test gets stuck in the middle or torwards the end. It is not 
always the same test.

{quote}So if the stream is corrupted, the main process does not send a new test 
to run because it things the current one is pending and needs to wait till it 
has finished in forked VM. So if the stream is corrupted, the main process does 
not send a new test to run because it things the current one is pending and 
needs to wait till it has finished in forked VM.
{quote}

I understand that but it doesn't seem like the stream gets corrupted. What 
would be a corruption of the stream?

{quote}
Please check the target/surefire-reports in project flink-scala-shell of the 
particular build which has failed.
Is there any exception?
{quote}

I have only checked the file locally and it didn't contain any exceptions. 
However, the error only occurs on Travis and there the file is not saved. I 
could rerun the build and save the surefire-reports directory. There are not 
errors in the regular logs. Do I need to use any special flags for enabling 
debug logging in Surefire?

{quote}
We should switch to another comminucation channel, unlike std/out, for our 
commands e.g. file system but this would take longer to develop.
{quote}

That can also cause problems. We had to switch from Failsafe to Surefire for 
integration tests because Failsafe would not report failed tests (because of a 
buffer flushing bug in SUREFIRE-1127, we couldn't use Failsafe 2.19 because of 
classpath related issues). Seems like we're out of luck :/


> 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
>            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