[GEODE-4741] DUnit launches ChildVMs with hardcoded heap size

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Won't Fix
• Component/s: tests
• Labels: pull-request-available
• Assignee: Kirk Lund
• Reporter: Kirk Lund
• Created: 23/Feb/18 19:44
• Updated: 13/Mar/18 23:34
• Resolved: 09/Mar/18 17:47

Description

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.

Issue Links

• links to: GitHub Pull Request #1545