[
https://issues.apache.org/jira/browse/GEODE-3999?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16259874#comment-16259874
]
ASF subversion and git services commented on GEODE-3999:
--------------------------------------------------------
Commit a89fce1582ffc79ac9fd72bd3e840df26e83d0d6 in geode's branch
refs/heads/develop from [~khowe]
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=a89fce1 ]
GEODE-3999: Prevent prematurely running out of heap (#1078)
The heap size for test014GemFireServerJvmProcessTerminatesOnOutOfMemoryError
is marginally increased from 10M to 12M. This should allow sufficient
memory to start the servers, but not so much that the test takes too long
to force the OutOfMemoryError.
> CI Failure: LauncherLifecycleCommandsDUnitTest fails with OutOfMemoryError
> --------------------------------------------------------------------------
>
> Key: GEODE-3999
> URL: https://issues.apache.org/jira/browse/GEODE-3999
> Project: Geode
> Issue Type: Bug
> Components: ci, gfsh
> Reporter: Kenneth Howe
> Assignee: Kenneth Howe
>
> Test runs with a minimal heap size in order to force an out of memory
> condition. However the size of the heap is so small that the out of memory
> occurs prematurely, before the server is initialized.
> {code:title=Stack from geode-ightly-flaky #177}
> org.apache.geode.management.internal.cli.commands.LauncherLifecycleCommandsDUnitTest
> > test014GemFireServerJvmProcessTerminatesOnOutOfMemoryError FAILED
> java.lang.AssertionError
> at org.junit.Assert.fail(Assert.java:86)
> at org.junit.Assert.assertTrue(Assert.java:41)
> at org.junit.Assert.assertTrue(Assert.java:52)
> at
> org.apache.geode.management.internal.cli.commands.LauncherLifecycleCommandsDUnitTest.test014GemFireServerJvmProcessTerminatesOnOutOfMemoryError(LauncherLifecycleCommandsDUnitTest.java:1018)
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)