You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@geode.apache.org by "Kirk Lund (JIRA)" <ji...@apache.org> on 2018/02/23 19:45:00 UTC

[jira] [Assigned] (GEODE-4741) DUnit launches ChildVMs with hardcoded heap size

     [ https://issues.apache.org/jira/browse/GEODE-4741?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Kirk Lund reassigned GEODE-4741:
--------------------------------

    Assignee: Kirk Lund

> DUnit launches ChildVMs with hardcoded heap size
> ------------------------------------------------
>
>                 Key: GEODE-4741
>                 URL: https://issues.apache.org/jira/browse/GEODE-4741
>             Project: Geode
>          Issue Type: Bug
>          Components: tests
>            Reporter: Kirk Lund
>            Assignee: Kirk Lund
>            Priority: Major
>
> This can result in tests such as PRQueryDUnitTest.testQueryResultsFromMembers passing in gradle but failing in an IDE such as IntelliJ. 
> Adding -Xmx to the JUnit configuration for PRQueryDUnitTest.testQueryResultsFromMembers in IntelliJ causes this test to start passing. Moving the code in testQueryResultsFromMembers from the JUnit controller JVM to a ChildVM also causes the test to start passing (because all 3 datastores are sized equivalently instead of having one be different size).
> The better solution is to change DUnit's ProcessManager to launch ChildVMs with the same heap size as the main JUnit controller JVM. Then they will always be equivalent in all environments.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)