You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@maven.apache.org by "nkeywal (JIRA)" <ji...@codehaus.org> on 2011/12/08 22:17:39 UTC

[jira] Updated: (SUREFIRE-799) Allow test parallelisation when forkMode=always

     [ https://jira.codehaus.org/browse/SUREFIRE-799?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

nkeywal updated SUREFIRE-799:
-----------------------------

    Attachment: surefire_799_212_trunk.patch

> Allow test parallelisation when forkMode=always
> -----------------------------------------------
>
>                 Key: SUREFIRE-799
>                 URL: https://jira.codehaus.org/browse/SUREFIRE-799
>             Project: Maven Surefire
>          Issue Type: Improvement
>          Components: process forking
>    Affects Versions: 2.10
>         Environment: all
>            Reporter: nkeywal
>         Attachments: surefire_799_212_trunk.patch
>
>
> Surefire already allows:
> - forking
> - parallelization within a JVM
> Mixing both features would mean forking multiple JVM instead of only one.
> It would allow to parallelize tests that need to be executed in a separate JVM (i.e.: with forkMode=always). Usually these tests take longer than the simple ones. In our case, 40% of the tests are executed in 4 minutes, the other 60% need two hours. So it's obviously more interesting to parallelize the former, but these ones need to fork.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira