You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Kristian Rosenvold (JIRA)" <ji...@codehaus.org> on 2012/08/01 11:51:21 UTC
[jira] (SUREFIRE-894) Do not fork process when there are no tests
to run (for forkMode=once)
Kristian Rosenvold created SUREFIRE-894:
-------------------------------------------
Summary: Do not fork process when there are no tests to run (for forkMode=once)
Key: SUREFIRE-894
URL: https://jira.codehaus.org/browse/SUREFIRE-894
Project: Maven Surefire
Issue Type: Improvement
Reporter: Kristian Rosenvold
When running forkmode="once", surefire always forks a process, since the scanning process is performed inside the fork.
On my machine, this effectively means surefire will ALWAYS spent around 125ms as a minimum execution time. This can easily add a couple of seconds to my build time since I have several modules without tests (api modules, war modules etc)
--
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-894) Do not fork process when there are no tests
to run (for forkMode=once)
Posted by "Kristian Rosenvold (JIRA)" <ji...@codehaus.org>.
[ https://jira.codehaus.org/browse/SUREFIRE-894?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Kristian Rosenvold closed SUREFIRE-894.
---------------------------------------
Resolution: Fixed
Fix Version/s: 2.12.2
Assignee: Kristian Rosenvold
Fixed in 2.12.2
> Do not fork process when there are no tests to run (for forkMode=once)
> ----------------------------------------------------------------------
>
> Key: SUREFIRE-894
> URL: https://jira.codehaus.org/browse/SUREFIRE-894
> Project: Maven Surefire
> Issue Type: Improvement
> Reporter: Kristian Rosenvold
> Assignee: Kristian Rosenvold
> Fix For: 2.12.2
>
>
> When running forkmode="once", surefire always forks a process, since the scanning process is performed inside the fork.
> On my machine, this effectively means surefire will ALWAYS spent around 125ms as a minimum execution time. This can easily add a couple of seconds to my build time since I have several modules without tests (api modules, war modules etc)
--
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-894) Do not fork process when there are no tests
to run (for forkMode=once)
Posted by "Kristian Rosenvold (JIRA)" <ji...@codehaus.org>.
[ https://jira.codehaus.org/browse/SUREFIRE-894?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=305581#comment-305581 ]
Kristian Rosenvold edited comment on SUREFIRE-894 at 8/5/12 5:47 AM:
---------------------------------------------------------------------
Fixed in r1369548
was (Author: krosenvold):
Fixed in 2.12.2
> Do not fork process when there are no tests to run (for forkMode=once)
> ----------------------------------------------------------------------
>
> Key: SUREFIRE-894
> URL: https://jira.codehaus.org/browse/SUREFIRE-894
> Project: Maven Surefire
> Issue Type: Improvement
> Reporter: Kristian Rosenvold
> Assignee: Kristian Rosenvold
> Fix For: 2.12.2
>
>
> When running forkmode="once", surefire always forks a process, since the scanning process is performed inside the fork.
> On my machine, this effectively means surefire will ALWAYS spent around 125ms as a minimum execution time. This can easily add a couple of seconds to my build time since I have several modules without tests (api modules, war modules etc)
--
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