[jira] (SUREFIRE-751) Support parallel/fork mode similar to http://maven-junit-plugin.kenai.com/
[ https://jira.codehaus.org/browse/SUREFIRE-751?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=321682#comment-321682 ] Jesse Glick commented on SUREFIRE-751: -- Thanks, this makes it much clearer. > Support parallel/fork mode similar to http://maven-junit-plugin.kenai.com/ > -- > > Key: SUREFIRE-751 > URL: https://jira.codehaus.org/browse/SUREFIRE-751 > Project: Maven Surefire > Issue Type: New Feature > Components: process forking >Affects Versions: 2.9 >Reporter: Stephen Connolly >Assignee: Kristian Rosenvold > Fix For: 2.13 > > Attachments: SUREFIRE-751-part1.patch, SUREFIRE-751-part2.patch > > > The current parallel execution spawns one thread _per_class_ > When there is a large disparity between the number of tests in different > classes, this can result in a longer execution time. This can often happen in > GUI testing, where a couple of classes will contain a lot of long running > (but low cpu) test cases, and the remaining classes run fast. > See http://maven-junit-plugin.kenai.com/ for an attempt at solving this -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (SUREFIRE-751) Support parallel/fork mode similar to http://maven-junit-plugin.kenai.com/
[ https://jira.codehaus.org/browse/SUREFIRE-751?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=321680#comment-321680 ] Andreas Gudian edited comment on SUREFIRE-751 at 3/8/13 2:36 PM: - There it is: http://maven.apache.org/surefire/maven-surefire-plugin/examples/fork-options-and-parallel-execution.html was (Author: agudian): The website of 2.14 is not yet in place, but you can preview it here: http://maven.apache.org/surefire-archives/maven-surefire-2.14/maven-surefire-plugin/examples/fork-options-and-parallel-execution.html The correct URL later on will be: http://maven.apache.org/surefire/maven-surefire-plugin/examples/fork-options-and-parallel-execution.html > Support parallel/fork mode similar to http://maven-junit-plugin.kenai.com/ > -- > > Key: SUREFIRE-751 > URL: https://jira.codehaus.org/browse/SUREFIRE-751 > Project: Maven Surefire > Issue Type: New Feature > Components: process forking >Affects Versions: 2.9 >Reporter: Stephen Connolly >Assignee: Kristian Rosenvold > Fix For: 2.13 > > Attachments: SUREFIRE-751-part1.patch, SUREFIRE-751-part2.patch > > > The current parallel execution spawns one thread _per_class_ > When there is a large disparity between the number of tests in different > classes, this can result in a longer execution time. This can often happen in > GUI testing, where a couple of classes will contain a lot of long running > (but low cpu) test cases, and the remaining classes run fast. > See http://maven-junit-plugin.kenai.com/ for an attempt at solving this -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (SUREFIRE-751) Support parallel/fork mode similar to http://maven-junit-plugin.kenai.com/
[ https://jira.codehaus.org/browse/SUREFIRE-751?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=321680#comment-321680 ] Andreas Gudian commented on SUREFIRE-751: - The website of 2.14 is not yet in place, but you can preview it here: http://maven.apache.org/surefire-archives/maven-surefire-2.14/maven-surefire-plugin/examples/fork-options-and-parallel-execution.html The correct URL later on will be: http://maven.apache.org/surefire/maven-surefire-plugin/examples/fork-options-and-parallel-execution.html > Support parallel/fork mode similar to http://maven-junit-plugin.kenai.com/ > -- > > Key: SUREFIRE-751 > URL: https://jira.codehaus.org/browse/SUREFIRE-751 > Project: Maven Surefire > Issue Type: New Feature > Components: process forking >Affects Versions: 2.9 >Reporter: Stephen Connolly >Assignee: Kristian Rosenvold > Fix For: 2.13 > > Attachments: SUREFIRE-751-part1.patch, SUREFIRE-751-part2.patch > > > The current parallel execution spawns one thread _per_class_ > When there is a large disparity between the number of tests in different > classes, this can result in a longer execution time. This can often happen in > GUI testing, where a couple of classes will contain a lot of long running > (but low cpu) test cases, and the remaining classes run fast. > See http://maven-junit-plugin.kenai.com/ for an attempt at solving this -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (SUREFIRE-751) Support parallel/fork mode similar to http://maven-junit-plugin.kenai.com/
[ https://jira.codehaus.org/browse/SUREFIRE-751?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=321675#comment-321675 ] Jesse Glick commented on SUREFIRE-751: -- @agudian: any progress on your examples page? Struggling the digest the implications of SUREFIRE-949. > Support parallel/fork mode similar to http://maven-junit-plugin.kenai.com/ > -- > > Key: SUREFIRE-751 > URL: https://jira.codehaus.org/browse/SUREFIRE-751 > Project: Maven Surefire > Issue Type: New Feature > Components: process forking >Affects Versions: 2.9 >Reporter: Stephen Connolly >Assignee: Kristian Rosenvold > Fix For: 2.13 > > Attachments: SUREFIRE-751-part1.patch, SUREFIRE-751-part2.patch > > > The current parallel execution spawns one thread _per_class_ > When there is a large disparity between the number of tests in different > classes, this can result in a longer execution time. This can often happen in > GUI testing, where a couple of classes will contain a lot of long running > (but low cpu) test cases, and the remaining classes run fast. > See http://maven-junit-plugin.kenai.com/ for an attempt at solving this -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (SUREFIRE-751) Support parallel/fork mode similar to http://maven-junit-plugin.kenai.com/
[ https://jira.codehaus.org/browse/SUREFIRE-751?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=316629#comment-316629 ] Kristian Rosenvold commented on SUREFIRE-751: - SUREFIRE-949 created, which will go into the next version > Support parallel/fork mode similar to http://maven-junit-plugin.kenai.com/ > -- > > Key: SUREFIRE-751 > URL: https://jira.codehaus.org/browse/SUREFIRE-751 > Project: Maven Surefire > Issue Type: New Feature > Components: process forking >Affects Versions: 2.9 >Reporter: Stephen Connolly >Assignee: Kristian Rosenvold > Fix For: 2.13 > > Attachments: SUREFIRE-751-part1.patch, SUREFIRE-751-part2.patch > > > The current parallel execution spawns one thread _per_class_ > When there is a large disparity between the number of tests in different > classes, this can result in a longer execution time. This can often happen in > GUI testing, where a couple of classes will contain a lot of long running > (but low cpu) test cases, and the remaining classes run fast. > See http://maven-junit-plugin.kenai.com/ for an attempt at solving this -- 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-751) Support parallel/fork mode similar to http://maven-junit-plugin.kenai.com/
[ https://jira.codehaus.org/browse/SUREFIRE-751?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=316618#comment-316618 ] Kristian Rosenvold commented on SUREFIRE-751: - If we ever get to support full symmetry of options (i.e. forkMode=perthread, parallel=classes, threadCount=2 we'd probably have to add a forkCount option too.) @andreas I'll look at your doc pull request "soon"; i have a feeling 2.13.1 is not too far off. (With a ".13" version number I suppose that's just to be expected) > Support parallel/fork mode similar to http://maven-junit-plugin.kenai.com/ > -- > > Key: SUREFIRE-751 > URL: https://jira.codehaus.org/browse/SUREFIRE-751 > Project: Maven Surefire > Issue Type: New Feature > Components: process forking >Affects Versions: 2.9 >Reporter: Stephen Connolly >Assignee: Kristian Rosenvold > Fix For: 2.13 > > Attachments: SUREFIRE-751-part1.patch, SUREFIRE-751-part2.patch > > > The current parallel execution spawns one thread _per_class_ > When there is a large disparity between the number of tests in different > classes, this can result in a longer execution time. This can often happen in > GUI testing, where a couple of classes will contain a lot of long running > (but low cpu) test cases, and the remaining classes run fast. > See http://maven-junit-plugin.kenai.com/ for an attempt at solving this -- 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-751) Support parallel/fork mode similar to http://maven-junit-plugin.kenai.com/
[
https://jira.codehaus.org/browse/SUREFIRE-751?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=316587#comment-316587
]
Andreas Gudian commented on SUREFIRE-751:
-
It is a duplicate, but the implementation ended up kind of different. What's
described in the last example (the one called perthreadOnce) is achieved by
using {{forkMode=perthread}}, {{reuseForks=true}} and some value >1 for
{{threadCount}}.
> Support parallel/fork mode similar to http://maven-junit-plugin.kenai.com/
> --
>
> Key: SUREFIRE-751
> URL: https://jira.codehaus.org/browse/SUREFIRE-751
> Project: Maven Surefire
> Issue Type: New Feature
> Components: process forking
>Affects Versions: 2.9
>Reporter: Stephen Connolly
>Assignee: Kristian Rosenvold
> Fix For: 2.13
>
> Attachments: SUREFIRE-751-part1.patch, SUREFIRE-751-part2.patch
>
>
> The current parallel execution spawns one thread _per_class_
> When there is a large disparity between the number of tests in different
> classes, this can result in a longer execution time. This can often happen in
> GUI testing, where a couple of classes will contain a lot of long running
> (but low cpu) test cases, and the remaining classes run fast.
> See http://maven-junit-plugin.kenai.com/ for an attempt at solving this
--
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-751) Support parallel/fork mode similar to http://maven-junit-plugin.kenai.com/
[ https://jira.codehaus.org/browse/SUREFIRE-751?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=316586#comment-316586 ] Jesse Glick commented on SUREFIRE-751: -- Is SUREFIRE-882 just a duplicate of this issue? The explicit example in that issue is more helpful than the current mojo parameter documentation. > Support parallel/fork mode similar to http://maven-junit-plugin.kenai.com/ > -- > > Key: SUREFIRE-751 > URL: https://jira.codehaus.org/browse/SUREFIRE-751 > Project: Maven Surefire > Issue Type: New Feature > Components: process forking >Affects Versions: 2.9 >Reporter: Stephen Connolly >Assignee: Kristian Rosenvold > Fix For: 2.13 > > Attachments: SUREFIRE-751-part1.patch, SUREFIRE-751-part2.patch > > > The current parallel execution spawns one thread _per_class_ > When there is a large disparity between the number of tests in different > classes, this can result in a longer execution time. This can often happen in > GUI testing, where a couple of classes will contain a lot of long running > (but low cpu) test cases, and the remaining classes run fast. > See http://maven-junit-plugin.kenai.com/ for an attempt at solving this -- 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-751) Support parallel/fork mode similar to http://maven-junit-plugin.kenai.com/
[
https://jira.codehaus.org/browse/SUREFIRE-751?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=316581#comment-316581
]
Andreas Gudian commented on SUREFIRE-751:
-
What a coincedence: I'm just working on a new examples page wrapping up the
forking and parallel options.
As for {{parallel}} and {{forkMode=perthread}}, you can actually use them
together - to some extent:
{{parallel=classes}} will have no effect when using {{forkMode=always}} or
{{forkMode=perthread}}. {{parallel=methods}} would work, however. Classes are
executed in {{threadCount=X}} concurrent processes ({{forkMode=perthread}}),
each of the processes can then use the same number of X threads to execute the
methods of one class in parallel. The option {{perCoreThreadCount}} only has an
effect on the number of threads for method-concurrency, but not on the number
of forked processes.
> Support parallel/fork mode similar to http://maven-junit-plugin.kenai.com/
> --
>
> Key: SUREFIRE-751
> URL: https://jira.codehaus.org/browse/SUREFIRE-751
> Project: Maven Surefire
> Issue Type: New Feature
> Components: process forking
>Affects Versions: 2.9
>Reporter: Stephen Connolly
>Assignee: Kristian Rosenvold
> Fix For: 2.13
>
> Attachments: SUREFIRE-751-part1.patch, SUREFIRE-751-part2.patch
>
>
> The current parallel execution spawns one thread _per_class_
> When there is a large disparity between the number of tests in different
> classes, this can result in a longer execution time. This can often happen in
> GUI testing, where a couple of classes will contain a lot of long running
> (but low cpu) test cases, and the remaining classes run fast.
> See http://maven-junit-plugin.kenai.com/ for an attempt at solving this
--
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-751) Support parallel/fork mode similar to http://maven-junit-plugin.kenai.com/
[
https://jira.codehaus.org/browse/SUREFIRE-751?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=316581#comment-316581
]
Andreas Gudian edited comment on SUREFIRE-751 at 1/3/13 2:49 PM:
-
What a coincidence: I'm just working on a new examples page wrapping up the
forking and parallel options.
As for {{parallel}} and {{forkMode=perthread}}, you can actually use them
together - to some extent:
{{parallel=classes}} will have no effect when using {{forkMode=always}} or
{{forkMode=perthread}}. {{parallel=methods}} would work, however. Classes are
executed in {{threadCount=X}} concurrent processes ({{forkMode=perthread}}),
each of the processes can then use the same number of X threads to execute the
methods of one class in parallel. The option {{perCoreThreadCount}} only has an
effect on the number of threads for method-concurrency, but not on the number
of forked processes.
was (Author: agudian):
What a coincedence: I'm just working on a new examples page wrapping up the
forking and parallel options.
As for {{parallel}} and {{forkMode=perthread}}, you can actually use them
together - to some extent:
{{parallel=classes}} will have no effect when using {{forkMode=always}} or
{{forkMode=perthread}}. {{parallel=methods}} would work, however. Classes are
executed in {{threadCount=X}} concurrent processes ({{forkMode=perthread}}),
each of the processes can then use the same number of X threads to execute the
methods of one class in parallel. The option {{perCoreThreadCount}} only has an
effect on the number of threads for method-concurrency, but not on the number
of forked processes.
> Support parallel/fork mode similar to http://maven-junit-plugin.kenai.com/
> --
>
> Key: SUREFIRE-751
> URL: https://jira.codehaus.org/browse/SUREFIRE-751
> Project: Maven Surefire
> Issue Type: New Feature
> Components: process forking
>Affects Versions: 2.9
>Reporter: Stephen Connolly
>Assignee: Kristian Rosenvold
> Fix For: 2.13
>
> Attachments: SUREFIRE-751-part1.patch, SUREFIRE-751-part2.patch
>
>
> The current parallel execution spawns one thread _per_class_
> When there is a large disparity between the number of tests in different
> classes, this can result in a longer execution time. This can often happen in
> GUI testing, where a couple of classes will contain a lot of long running
> (but low cpu) test cases, and the remaining classes run fast.
> See http://maven-junit-plugin.kenai.com/ for an attempt at solving this
--
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-751) Support parallel/fork mode similar to http://maven-junit-plugin.kenai.com/
[
https://jira.codehaus.org/browse/SUREFIRE-751?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=316579#comment-316579
]
Jesse Glick commented on SUREFIRE-751:
--
Getting harder to keep track of the different thread-related options; what is
the interaction between {{parallel}} and {{forkmode="perthread"}}?
http://maven.apache.org/surefire/maven-surefire-plugin/examples/junit.html
mentions parallelism but not (in this context) forking.
> Support parallel/fork mode similar to http://maven-junit-plugin.kenai.com/
> --
>
> Key: SUREFIRE-751
> URL: https://jira.codehaus.org/browse/SUREFIRE-751
> Project: Maven Surefire
> Issue Type: New Feature
> Components: process forking
>Affects Versions: 2.9
>Reporter: Stephen Connolly
>Assignee: Kristian Rosenvold
> Fix For: 2.13
>
> Attachments: SUREFIRE-751-part1.patch, SUREFIRE-751-part2.patch
>
>
> The current parallel execution spawns one thread _per_class_
> When there is a large disparity between the number of tests in different
> classes, this can result in a longer execution time. This can often happen in
> GUI testing, where a couple of classes will contain a lot of long running
> (but low cpu) test cases, and the remaining classes run fast.
> See http://maven-junit-plugin.kenai.com/ for an attempt at solving this
--
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-751) Support parallel/fork mode similar to http://maven-junit-plugin.kenai.com/
[ https://jira.codehaus.org/browse/SUREFIRE-751?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andreas Gudian updated SUREFIRE-751: Attachment: SUREFIRE-751-part2.patch SUREFIRE-751-part1.patch For the record: attached the content of the two pull requests that contained the original patch. > Support parallel/fork mode similar to http://maven-junit-plugin.kenai.com/ > -- > > Key: SUREFIRE-751 > URL: https://jira.codehaus.org/browse/SUREFIRE-751 > Project: Maven Surefire > Issue Type: New Feature > Components: process forking >Affects Versions: 2.9 >Reporter: Stephen Connolly >Assignee: Kristian Rosenvold > Fix For: 2.13 > > Attachments: SUREFIRE-751-part1.patch, SUREFIRE-751-part2.patch > > > The current parallel execution spawns one thread _per_class_ > When there is a large disparity between the number of tests in different > classes, this can result in a longer execution time. This can often happen in > GUI testing, where a couple of classes will contain a lot of long running > (but low cpu) test cases, and the remaining classes run fast. > See http://maven-junit-plugin.kenai.com/ for an attempt at solving this -- 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-751) Support parallel/fork mode similar to http://maven-junit-plugin.kenai.com/
[ https://jira.codehaus.org/browse/SUREFIRE-751?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kristian Rosenvold closed SUREFIRE-751. --- Resolution: Fixed Fix Version/s: (was: 3.0) 2.13 Fixed 9c6ce9be423219e88d6e9c777ba69eea5e831d0c and 05aa3a60015883588f47f48a8bc92a05c1efb075, patch by Andreas Gudian. Please note that I'm considering changing forkMode="onceperthread" (as implemented by this patch) to an additional attribute "reuseForks" and remove "onceperthread" before 2.13 is released. (reuseForks could have a future mode of "reactor" which could re-use the forked process across modules in a reactor build) > Support parallel/fork mode similar to http://maven-junit-plugin.kenai.com/ > -- > > Key: SUREFIRE-751 > URL: https://jira.codehaus.org/browse/SUREFIRE-751 > Project: Maven Surefire > Issue Type: New Feature > Components: process forking >Affects Versions: 2.9 >Reporter: Stephen Connolly >Assignee: Kristian Rosenvold > Fix For: 2.13 > > > The current parallel execution spawns one thread _per_class_ > When there is a large disparity between the number of tests in different > classes, this can result in a longer execution time. This can often happen in > GUI testing, where a couple of classes will contain a lot of long running > (but low cpu) test cases, and the remaining classes run fast. > See http://maven-junit-plugin.kenai.com/ for an attempt at solving this -- 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
