[jira] [Commented] (SUREFIRE-1246) Surefire + Cobertura: Shutdown of Forked JVM timeouts before all thread ends

["Tibor Digana (JIRA)" <ji...@apache.org>]

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

Tibor Digana commented on SUREFIRE-1246:
----------------------------------------

[~ipinheiro]
We can introduce a parameter forkedProcessExitTimeoutInSeconds which will be standing in the list very close to
https://maven.apache.org/surefire/maven-surefire-plugin/test-mojo.html#forkedProcessTimeoutInSeconds

The parameter forkedProcessExitTimeoutInSeconds might be specified as follows:
Kill the forked test process after finished test-set executed java.lang.System.exit(int) times out a certain number of seconds. If set to 0, wait forever for the process, never timing out.

> Surefire + Cobertura: Shutdown of Forked JVM timeouts before all thread ends
> ----------------------------------------------------------------------------
>
>                 Key: SUREFIRE-1246
>                 URL: https://issues.apache.org/jira/browse/SUREFIRE-1246
>             Project: Maven Surefire
>          Issue Type: Improvement
>          Components: Maven Surefire Plugin
>    Affects Versions: 2.19.1
>            Reporter: Ivo Pinheiro
>            Assignee: Tibor Digana
>
> There should be a possibility to configure the Embedded shutdown timeout, to a value greater than 30 seconds.
> When using cobertura to evaluate the code coverage, and with a big number of tests to run, the surefire plugin does not wait for cobertura writes all cobertura information to cobertura.ser because the 30 seconds embedded shutdown timeout is not sufficient.
> Is it possible to add a configuration property to surefire-plugin to configure the embedded timeout time?



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