You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Tibor Digana (JIRA)" <ji...@apache.org> on 2016/10/02 21:33:20 UTC
[jira] [Commented] (SUREFIRE-1246) Surefire + Cobertura: Shutdown
of Forked JVM timeouts before all thread ends
[ https://issues.apache.org/jira/browse/SUREFIRE-1246?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15541016#comment-15541016 ]
Tibor Digana commented on SUREFIRE-1246:
----------------------------------------
https://git-wip-us.apache.org/repos/asf?p=maven-surefire.git;a=commit;h=9dc15743de2c9ba189837d41752cf973507d6c31
> 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 Failsafe Plugin, Maven Surefire Plugin
> Affects Versions: 2.19.1
> Reporter: Ivo Pinheiro
> Assignee: Tibor Digana
> Fix For: 2.19.2
>
>
> 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)