maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ivo Pinheiro (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (SUREFIRE-1246) Surefire + Cobertura: Shutdown of Forked JVM timeouts before all thread ends
Date Mon, 09 May 2016 22:38:12 GMT

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

Ivo Pinheiro commented on SUREFIRE-1246:
----------------------------------------

[~tibor17] thank for your quick response. 
The solucionar you haver proposed seems that will work, and will be flexible according the
developers needs.
When do you think this chance will be available on a release? 

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

Mime
View raw message