maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Andreas Gudian (JIRA)" <j...@codehaus.org>
Subject [jira] (SUREFIRE-751) Support parallel/fork mode similar to http://maven-junit-plugin.kenai.com/
Date Thu, 03 Jan 2013 20:50:13 GMT

    [ 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

        

Mime
View raw message