[
https://jira.codehaus.org/browse/SUREFIRE-799?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=289612#comment-289612
]
nkeywal commented on SUREFIRE-799:
----------------------------------
Yes, I confirm it will relaunch a new jvm for each test. Kristian's comment
above says "reusable forks" are in the roadmap. It's not something we need, so
I didn't look at it when I implemented the patch. BTW you can parallelize the
tests with forkMode=once, and in this case the jvm is not recreated.
> Allow test parallelisation when forkMode=always
> -----------------------------------------------
>
> Key: SUREFIRE-799
> URL: https://jira.codehaus.org/browse/SUREFIRE-799
> Project: Maven Surefire
> Issue Type: New Feature
> Components: process forking
> Affects Versions: 2.10
> Environment: all
> Reporter: nkeywal
> Assignee: Kristian Rosenvold
> Fix For: 2.12
>
> Attachments: surefire_799_212_trunk.patch, surefire_799.v2.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.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
