[ http://jira.codehaus.org/browse/SUREFIRE-735?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=266012#action_266012 ]
Kristian Rosenvold edited comment on SUREFIRE-735 at 5/8/11 1:33 PM: --------------------------------------------------------------------- Which version of surefire and which OS is this on ? I am unable to reproduce this with any version of surefire on linux or windows Make sure you also try the latest released version (2.8.1) if you haven't done so was (Author: krosenvold): Which version of surefire and which OS is this on ? I am unable to reproduce this with any version of surefire on linux. Make sure you also try the latest released version (2.8.1) if you haven't done so > Surefire plugin does not report fatal VM creation failure > --------------------------------------------------------- > > Key: SUREFIRE-735 > URL: http://jira.codehaus.org/browse/SUREFIRE-735 > Project: Maven Surefire > Issue Type: Bug > Reporter: James Phillpotts > > Background: > In a large project with a lot of test classes and classes under test, memory > settings have been tuned to prevent test failure. However, Java is fussy > about some memory settings, and if it cannot allocate the amount of memory > needed, the VM will fail to start. > Problem: > When surefire encounters this failure to start, the problem is reported to > the user as follows: > {noformat} > [INFO] > ------------------------------------------------------------------------ > [ERROR] BUILD FAILURE > [INFO] > ------------------------------------------------------------------------ > [INFO] There are test failures. > Please refer to [snip]\target\surefire-reports for the individual test > results. > {noformat} > The surefire-reports directory does not exist within target. > Using debug mode, the command that is executed is found, and when run from a > command prompt window, the following output is received: > {noformat} > Error occurred during initialization of VM > Could not reserve enough space for object heap > Could not create the Java virtual machine. > {noformat} > Obviously there is nothing surefire can do about the failure to start the VM, > but the error output from the VM itself should be passed back to the user, so > that they can do something to remedy it. > I'd supply some steps to reproduce it, but as it would depend on the memory > available on the machine used to test it, they wouldn't necessarily work, but > by playing with the Xmx and Xms settings, it should be possible to duplicate > this. -- 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