db-derby-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bpendle...@apache.org
Subject svn commit: r562604 - /db/derby/code/trunk/build.xml
Date Fri, 03 Aug 2007 22:18:43 GMT
Author: bpendleton
Date: Fri Aug  3 15:18:40 2007
New Revision: 562604

URL: http://svn.apache.org/viewvc?view=rev&rev=562604
Log:
DERBY-2988: Add max heap memory setting for spawned JVM in junitreport target

This patch was contributed by John Embretsen (John dot Embretsen at Sun dot com)

This change adds a max heap size setting in the junit-core target of the
top-level build.xml file. The setting is:

   maxmemory="512m"

This eliminates junitreport-related OutOfMemoryErrors.

Modified:
    db/derby/code/trunk/build.xml

Modified: db/derby/code/trunk/build.xml
URL: http://svn.apache.org/viewvc/db/derby/code/trunk/build.xml?view=diff&rev=562604&r1=562603&r2=562604
==============================================================================
--- db/derby/code/trunk/build.xml (original)
+++ db/derby/code/trunk/build.xml Fri Aug  3 15:18:40 2007
@@ -1694,9 +1694,14 @@
         <isset property="derby.junit.classpath"/>
       </not>
     </condition>
+         <!--
+         Specifying max heap size (maxmemory) for JVMs spawned by this
+         target, since the default max heap size on most systems is
+         currently too low for some of the test suites. See DERBY-2988.
+         -->
   	 <junit printsummary="on"
            fork="yes" forkmode="perTest"
-           jvm="${derby.junit.jvm}"
+           jvm="${derby.junit.jvm}" maxmemory="512m"
            showoutput="yes"
            dir="junit_${derby.junit.timestamp}"
   	 	   errorproperty="tests.failed"



Mime
View raw message