You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Eric Smalling (JIRA)" <ji...@codehaus.org> on 2008/03/04 00:09:28 UTC
[jira] Created: (SUREFIRE-465) Add numeric option for forkmode
param
Add numeric option for forkmode param
-------------------------------------
Key: SUREFIRE-465
URL: http://jira.codehaus.org/browse/SUREFIRE-465
Project: Maven Surefire
Issue Type: Improvement
Components: process forking
Reporter: Eric Smalling
Priority: Minor
PermGen memory becomes very full for large sets of junits. So much so that unless I turn on <forkmode>pertest</forkmode> I have to up my MaxPermGen to over 300m (we have 2600+ tests)
Since that slows the tests to a crawl, and since using that much perm space causes problems with virtual memory paging I'd like to see if an option to fork on every n-th test could be added.
ie: <forkmode>100</forkmode> would create a new fork for every 100 tests.
I'll dl the source and see if i can submit a patch here too.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (SUREFIRE-465) Add numeric option for forkmode param
Posted by "Kristian Rosenvold (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/SUREFIRE-465?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Kristian Rosenvold closed SUREFIRE-465.
---------------------------------------
Resolution: Won't Fix
http://mail-archives.apache.org/mod_mbox/maven-dev/201101.mbox/%3C1295866251.13332.27.camel@chunky%3E
> Add numeric option for forkmode param
> -------------------------------------
>
> Key: SUREFIRE-465
> URL: http://jira.codehaus.org/browse/SUREFIRE-465
> Project: Maven Surefire
> Issue Type: Improvement
> Components: process forking
> Reporter: Eric Smalling
> Priority: Minor
> Fix For: Backlog
>
>
> PermGen memory becomes very full for large sets of junits. So much so that unless I turn on <forkmode>pertest</forkmode> I have to up my MaxPermGen to over 300m (we have 2600+ tests)
> Since that slows the tests to a crawl, and since using that much perm space causes problems with virtual memory paging I'd like to see if an option to fork on every n-th test could be added.
> ie: <forkmode>100</forkmode> would create a new fork for every 100 tests.
> I'll dl the source and see if i can submit a patch here too.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (SUREFIRE-465) Add numeric option for forkmode
param
Posted by "Kristian Rosenvold (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/SUREFIRE-465?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=252627#action_252627 ]
Kristian Rosenvold commented on SUREFIRE-465:
---------------------------------------------
As of surefire 2.7, the provider itself controls the forking process (for forkMode != never and forkMode!= once) through the SurefireProvider interface. It should be trivial for anyone requiring this kind of behaviour to make their own provider, by just forking their current provider and modify the getSuites method. Proposing as wontfix.
> Add numeric option for forkmode param
> -------------------------------------
>
> Key: SUREFIRE-465
> URL: http://jira.codehaus.org/browse/SUREFIRE-465
> Project: Maven Surefire
> Issue Type: Improvement
> Components: process forking
> Reporter: Eric Smalling
> Priority: Minor
> Fix For: Backlog
>
>
> PermGen memory becomes very full for large sets of junits. So much so that unless I turn on <forkmode>pertest</forkmode> I have to up my MaxPermGen to over 300m (we have 2600+ tests)
> Since that slows the tests to a crawl, and since using that much perm space causes problems with virtual memory paging I'd like to see if an option to fork on every n-th test could be added.
> ie: <forkmode>100</forkmode> would create a new fork for every 100 tests.
> I'll dl the source and see if i can submit a patch here too.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (SUREFIRE-465) Add numeric option for forkmode param
Posted by "Brett Porter (JIRA)" <ji...@codehaus.org>.
[ https://jira.codehaus.org/browse/SUREFIRE-465?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Brett Porter updated SUREFIRE-465:
----------------------------------
Fix Version/s: (was: Backlog)
> Add numeric option for forkmode param
> -------------------------------------
>
> Key: SUREFIRE-465
> URL: https://jira.codehaus.org/browse/SUREFIRE-465
> Project: Maven Surefire
> Issue Type: Improvement
> Components: process forking
> Reporter: Eric Smalling
> Priority: Minor
>
> PermGen memory becomes very full for large sets of junits. So much so that unless I turn on <forkmode>pertest</forkmode> I have to up my MaxPermGen to over 300m (we have 2600+ tests)
> Since that slows the tests to a crawl, and since using that much perm space causes problems with virtual memory paging I'd like to see if an option to fork on every n-th test could be added.
> ie: <forkmode>100</forkmode> would create a new fork for every 100 tests.
> I'll dl the source and see if i can submit a patch here too.
--
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] Updated: (SUREFIRE-465) Add numeric option for forkmode
param
Posted by "Dan Fabulich (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/SUREFIRE-465?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Dan Fabulich updated SUREFIRE-465:
----------------------------------
Fix Version/s: Future
Perhaps more plausible might be to fork a process on a per-package basis.
> Add numeric option for forkmode param
> -------------------------------------
>
> Key: SUREFIRE-465
> URL: http://jira.codehaus.org/browse/SUREFIRE-465
> Project: Maven Surefire
> Issue Type: Improvement
> Components: process forking
> Reporter: Eric Smalling
> Priority: Minor
> Fix For: Future
>
>
> PermGen memory becomes very full for large sets of junits. So much so that unless I turn on <forkmode>pertest</forkmode> I have to up my MaxPermGen to over 300m (we have 2600+ tests)
> Since that slows the tests to a crawl, and since using that much perm space causes problems with virtual memory paging I'd like to see if an option to fork on every n-th test could be added.
> ie: <forkmode>100</forkmode> would create a new fork for every 100 tests.
> I'll dl the source and see if i can submit a patch here too.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira