[
https://issues.apache.org/jira/browse/OAK-2545?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14333216#comment-14333216
]
Alex Parvulescu commented on OAK-2545:
--------------------------------------
We should disable the test for now.
See my comment on OAK-2294 [0] the test is too heavy, but unfortunately that's
the only way to see if the repo gets corrupted or not.
[0]
https://issues.apache.org/jira/browse/OAK-2294?focusedCommentId=14326269&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-14326269
> oak-core IT run out of memory
> -----------------------------
>
> Key: OAK-2545
> URL: https://issues.apache.org/jira/browse/OAK-2545
> Project: Jackrabbit Oak
> Issue Type: Test
> Components: core
> Reporter: Marcel Reutegger
> Assignee: Marcel Reutegger
> Priority: Blocker
> Fix For: 1.0.12
>
>
> Seen on the 1.0 branch only so far when running ITs on my local machine, but
> travis reports the same:
> https://travis-ci.org/apache/jackrabbit-oak/builds/51589769
> It doesn't necessarily mean the problem is with SegmentReferenceLimitTestIT
> even though the heap dump shows most of the memory consumed by Segments and
> SegmentWriter. A recent build on trunk was successful for me where we have
> the same test.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
