[
https://issues.apache.org/jira/browse/GEODE-7489?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17275308#comment-17275308
]
Geode Integration commented on GEODE-7489:
------------------------------------------
Seen on support/1.12 in [IntegrationTestOpenJDK8
#107|https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-support-1-12-main/jobs/IntegrationTestOpenJDK8/builds/107]
... see [test
results|http://files.apachegeode-ci.info/builds/apache-support-1-12-main/1.12.1-build.0146/test-results/integrationTest/1606882590/]
or download
[artifacts|http://files.apachegeode-ci.info/builds/apache-support-1-12-main/1.12.1-build.0146/test-artifacts/1606882590/integrationtestfiles-OpenJDK8-1.12.1-build.0146.tgz].
> DistributionArchUnitTest is running out of memory for some users
> ----------------------------------------------------------------
>
> Key: GEODE-7489
> URL: https://issues.apache.org/jira/browse/GEODE-7489
> Project: Geode
> Issue Type: Bug
> Components: membership
> Reporter: Dan Smith
> Priority: Major
> Labels: no-release-note, pull-request-available
> Fix For: 1.14.0
>
> Time Spent: 40m
> Remaining Estimate: 0h
>
> This test ran out of memory when running ./gradlew build for some users. From
> the mailing list:
> {noformat}
> Any ideas why DistributionArchUnitTest would run OutOfMemoryError when
> doing a "./gradlew build"?
> I think we should move any unit tests that run OutOfMemoryError out of unit
> tests (to integration tests maybe?).
> > Task :geode:geode-core:test
> Heap dump file created [957877145 bytes in 17.227 secs]
> org.apache.geode.distributed.internal.DistributionArchUnitTest >
> classMethod FAILED
> java.lang.OutOfMemoryError: GC overhead limit exceeded
> 6991 tests completed, 1 failed, 12 skipped
> {noformat}
> This is a relatively new test that is scanning a lot of classes for
> dependencies, so it may have memory issues.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
