[jira] [Updated] (GEODE-7489) DistributionArchUnitTest is running out of memory for some users
[ https://issues.apache.org/jira/browse/GEODE-7489?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bill Burcham updated GEODE-7489: Fix Version/s: (was: 1.12.0) 1.14.0 > 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)
[jira] [Updated] (GEODE-7489) DistributionArchUnitTest is running out of memory for some users
[ https://issues.apache.org/jira/browse/GEODE-7489?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bruce J Schuchardt updated GEODE-7489: -- Labels: no-release-note pull-request-available (was: pull-request-available) > 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.12.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)
[jira] [Updated] (GEODE-7489) DistributionArchUnitTest is running out of memory for some users
[ https://issues.apache.org/jira/browse/GEODE-7489?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated GEODE-7489: -- Labels: pull-request-available (was: ) > 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: pull-request-available > Fix For: 1.12.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)
[jira] [Updated] (GEODE-7489) DistributionArchUnitTest is running out of memory for some users
[ https://issues.apache.org/jira/browse/GEODE-7489?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bruce J Schuchardt updated GEODE-7489: -- Fix Version/s: 1.12.0 > 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 >Assignee: Bruce J Schuchardt >Priority: Major > Fix For: 1.12.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)