[
https://issues.apache.org/jira/browse/GEODE-5615?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16589399#comment-16589399
]
ASF subversion and git services commented on GEODE-5615:
--------------------------------------------------------
Commit 5602d02800e694afaaa08230e83df4d5c4bffb2e in geode's branch
refs/heads/develop from Dan Smith
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=5602d02 ]
GEODE-5615: Capturing more data in the case of hangs or OOMEs
To help us track down builds that fail with OutOfMemory errors, capture
any hprof files found.
Capturing call stacks for all java processes
We were only capturing the call stacks for ChildVM processes, which
doesn't include the main test JVM.
> Many DistributedTest runs are failing with OutOfMemoryError
> -----------------------------------------------------------
>
> Key: GEODE-5615
> URL: https://issues.apache.org/jira/browse/GEODE-5615
> Project: Geode
> Issue Type: Bug
> Reporter: Dan Smith
> Assignee: Dan Smith
> Priority: Major
> Labels: pull-request-available, swat
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> Many of our concourse runs are failing with OutOfMemoryErrors.
> https://concourse.apachegeode-ci.info/teams/main/pipelines/develop/jobs/DistributedTest/builds/283
> The first failure seems to be this build. Something must have changed
> recently to start causing this:
> https://concourse.apachegeode-ci.info/teams/main/pipelines/develop/jobs/DistributedTest/builds/274
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
