[jira] (SUREFIRE-799) Allow test parallelisation when forkMode=always
[ https://jira.codehaus.org/browse/SUREFIRE-799?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=291341#comment-291341 ] Martin Burger commented on SUREFIRE-799: JUnit test parallelization with forkMode=always is supposed to work now? On my machine (I use Maven Surefire 2.12), with 'always' tests are not run in parallel (although log messages on the console suggest parallel test execution). When I use 'perthread' as forkMode instead, tests are actually run in parallel. 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
[jira] (SUREFIRE-799) Allow test parallelisation when forkMode=always
[ https://jira.codehaus.org/browse/SUREFIRE-799?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=291342#comment-291342 ] Kristian Rosenvold commented on SUREFIRE-799: - always is linear, single threaded as before. 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
[jira] (SUREFIRE-799) Allow test parallelisation when forkMode=always
[
https://jira.codehaus.org/browse/SUREFIRE-799?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=289606#comment-289606
]
Alexey Yudichev commented on SUREFIRE-799:
--
Thanks nkeywal, one question if you don't mind. I want surefire to fork X JVMs
and then spread the tests across them evenly without re-launching new JVM for
every test. Look like this:{code:xml}
configuration
forkModeperthread/forkMode
threadCount2/threadCount
/configuration{code}
runs at most 2 JVMs but still launches new JVM instance for every test. Is it
possible to reuse JVMs? Our integration tests are heavy to initialise and their
initialisation is statically defined, so to avoid re-initialisation there
should be JVM reuse.
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
[jira] (SUREFIRE-799) Allow test parallelisation when forkMode=always
[
https://jira.codehaus.org/browse/SUREFIRE-799?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=289606#comment-289606
]
Alexey Yudichev edited comment on SUREFIRE-799 at 1/25/12 4:35 AM:
---
Thanks nkeywal, one question if you don't mind. I want surefire to fork X JVMs
and then spread the tests across them evenly without re-launching new JVM for
every test. Looks like this:{code:xml}
configuration
forkModeperthread/forkMode
threadCount2/threadCount
/configuration{code}
runs at most 2 JVMs but still launches new JVM instance for every test. Is it
possible to reuse JVMs? Our integration tests are heavy to initialise and their
initialisation is statically defined, so to avoid re-initialisation there
should be JVM reuse.
was (Author: ylexus):
Thanks nkeywal, one question if you don't mind. I want surefire to fork X
JVMs and then spread the tests across them evenly without re-launching new JVM
for every test. Look like this:{code:xml}
configuration
forkModeperthread/forkMode
threadCount2/threadCount
/configuration{code}
runs at most 2 JVMs but still launches new JVM instance for every test. Is it
possible to reuse JVMs? Our integration tests are heavy to initialise and their
initialisation is statically defined, so to avoid re-initialisation there
should be JVM reuse.
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
[jira] (SUREFIRE-799) Allow test parallelisation when forkMode=always
[ https://jira.codehaus.org/browse/SUREFIRE-799?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=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
[jira] (SUREFIRE-799) Allow test parallelisation when forkMode=always
[ https://jira.codehaus.org/browse/SUREFIRE-799?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=289618#comment-289618 ] Alexey Yudichev commented on SUREFIRE-799: -- Yes, but forkMode=once will only parallelise tests within same JVM using multiple threads, which will not work for us as our tests are inherently not thread safe. We need 1 thread multiple JVMs type of parallelisation with JVM reuse. I'll think of some workaround in this case. 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
[jira] (SUREFIRE-799) Allow test parallelisation when forkMode=always
[ https://jira.codehaus.org/browse/SUREFIRE-799?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=289622#comment-289622 ] Kristian Rosenvold commented on SUREFIRE-799: - Re-using VM's is a planned feature, but someone has to implement it ;) 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
[jira] (SUREFIRE-799) Allow test parallelisation when forkMode=always
[ https://jira.codehaus.org/browse/SUREFIRE-799?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=289546#comment-289546 ] Alexey Yudichev commented on SUREFIRE-799: -- This is not yet in https://repository.apache.org/content/groups/snapshots/org/apache/maven/plugins/maven-surefire-plugin/2.12-SNAPSHOT/maven-surefire-plugin-2.12-20120119.191905-28.jar by the looks of it as I'm getting: Execution default-test of goal org.apache.maven.plugins:maven-surefire-plugin:2.12-SNAPSHOT:test failed: Fork mode perThread is not a legal value Any chance you can deploy a snapshot with this patch in? 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 Assignee: Kristian Rosenvold 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
[jira] (SUREFIRE-799) Allow test parallelisation when forkMode=always
[ https://jira.codehaus.org/browse/SUREFIRE-799?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=289548#comment-289548 ] nkeywal commented on SUREFIRE-799: -- Kristian renamed it to perthread in the trunk. It works well for us. 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 Assignee: Kristian Rosenvold 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
[jira] (SUREFIRE-799) Allow test parallelisation when forkMode=always
[ https://jira.codehaus.org/browse/SUREFIRE-799?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kristian Rosenvold updated SUREFIRE-799: Fix Version/s: 2.12 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 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
[jira] (SUREFIRE-799) Allow test parallelisation when forkMode=always
[ https://jira.codehaus.org/browse/SUREFIRE-799?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kristian Rosenvold updated SUREFIRE-799: Issue Type: New Feature (was: Improvement) 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
[jira] (SUREFIRE-799) Allow test parallelisation when forkMode=always
[ https://jira.codehaus.org/browse/SUREFIRE-799?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kristian Rosenvold closed SUREFIRE-799. --- Resolution: Fixed Fixed in r1222474, thanks for the patch! I made some adjustments to the patch, and you may want to look over those. 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 Assignee: Kristian Rosenvold 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
[jira] (SUREFIRE-799) Allow test parallelisation when forkMode=always
[ https://jira.codehaus.org/browse/SUREFIRE-799?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on SUREFIRE-799 started by Kristian Rosenvold. 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 Assignee: Kristian Rosenvold 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
[jira] (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.v2.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_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
[jira] (SUREFIRE-799) Allow test parallelisation when forkMode=always
[ https://jira.codehaus.org/browse/SUREFIRE-799?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=286121#comment-286121 ] nkeywal commented on SUREFIRE-799: -- v2 includes: - integration test with surefire-integration-tests/src/test/resources/runorder-parallel - forkMode is perThread - use threadCount 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_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
[jira] (SUREFIRE-799) Allow test parallelisation when forkMode=always
[ https://jira.codehaus.org/browse/SUREFIRE-799?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=285597#comment-285597 ] nkeywal commented on SUREFIRE-799: -- Ok, will do. Do you have something in mind for 2.12 release date? 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. 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
[jira] (SUREFIRE-799) Allow test parallelisation when forkMode=always
[ https://jira.codehaus.org/browse/SUREFIRE-799?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=285537#comment-285537 ] Kristian Rosenvold commented on SUREFIRE-799: - This is a cool patch;) It needs a few minor modifications; I think the regular threadCount parameter should be used, and the forkMode should be perthread. It also needs an integration test, you should be able to modify (or make a new project based on) surefire-integration-tests/src/test/resources/runorder-parallel and a test implementation in XmlReporterRunTimeIT. (I think you can just modify the existing to accept forkMode as a -D parameter instead of hard-coding) I will be releasing 2.11.1 soon, but I'll schedule this patch for 2.12 if you fix this stuff. 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. 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
