db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Bryan Pendleton (JIRA)" <j...@apache.org>
Subject [jira] Commented: (DERBY-2988) Add max heap memory setting for JVMs spawned when running ant junitreport
Date Thu, 02 Aug 2007 15:36:58 GMT

    [ https://issues.apache.org/jira/browse/DERBY-2988?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12517292

Bryan Pendleton commented on DERBY-2988:

Thanks John! This seems like a good idea to me. I'll have a look at committing this change
over the weekend. If anyone feels this is a bad idea, please let us know.

> Add max heap memory setting for JVMs spawned when running ant junitreport
> -------------------------------------------------------------------------
>                 Key: DERBY-2988
>                 URL: https://issues.apache.org/jira/browse/DERBY-2988
>             Project: Derby
>          Issue Type: Test
>          Components: Build tools, Test
>    Affects Versions:
>            Reporter: John H. Embretsen
>            Assignee: John H. Embretsen
>         Attachments: d2988_v1.diff, d2988_v1.stat
> Rationale for adding an explicit max heap size setting for JVMs spawned by ant when running
'ant junitreport':
> 1) To avoid running out of memory during runs of 'ant junitreport' on systems where the
default max heap size is too small for one or more test suites executed by the junitreport
target. For example, on client-class machines using Sun's JVM (version 1.6 or older) the default
max heap size is usually 64 MB. The lang._Suite junit test suite currently requires roughly
170 MB.
> This will reduce some unnecessary noise in the developers' regression test results.
> 2) To have the test suites run with consistent max heap size settings regardless of machine
class. By using default values, some machines/JVMs run with 64 MB max heap while others run
with 512 MB or more, resulting in memory-related test failures only in some environments.
This might complicate debugging.
> 3) Developers will have a better picture of the memory requirements of a test suite if
it should fail with OutOfMemoryError via 'ant junitreport'. Without this change, extra effort
(e.g. JVM monitoring) is required to know the exact value of the heap size limit that was
> A discussion on the derby-dev mailing list provides some more details: http://www.nabble.com/Do-I-need-to-provide-extra-memory-flags-when-using-%22ant-junitreport%22--t4139842.html

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message