You are viewing a plain text version of this content. The canonical link for it is here.
Posted to oak-issues@jackrabbit.apache.org by "Michael Dürig (JIRA)" <ji...@apache.org> on 2016/04/26 17:14:12 UTC
[jira] [Commented] (OAK-4312) Fix test failures in
SegmentDataStoreBlobGCIT
[ https://issues.apache.org/jira/browse/OAK-4312?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15258240#comment-15258240 ]
Michael Dürig commented on OAK-4312:
------------------------------------
http://svn.apache.org/viewvc?rev=1741053&view=rev: ignored the failing test for now as we need a fix for OAK-4285 first.
> Fix test failures in SegmentDataStoreBlobGCIT
> ---------------------------------------------
>
> Key: OAK-4312
> URL: https://issues.apache.org/jira/browse/OAK-4312
> Project: Jackrabbit Oak
> Issue Type: Task
> Components: segment-next
> Reporter: Michael Dürig
> Labels: cleanup, gc
> Fix For: 1.6
>
>
> {{SegmentDataStoreBlobGCIT#gcWithInlined}}, {{gc}}, {{gcLongRunningBlobCollection}} and {{consistencyCheckWithGc}} fail since the removal of the old cleanup strategy in OAK-4276.
> The test setup needs to be adapted to the brutal strategy: i.e. {{setup()}} needs to simulate so many compaction cycles until a subsequent cleanup actually remove the segments in question.
> This is not sufficient though as then {{SegmentTracker#collectBlobReferences}} causes a SNFE for those segment ids actually removed but still in the segment id tables.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)