You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@mesos.apache.org by "Jie Yu (JIRA)" <ji...@apache.org> on 2018/01/04 17:55:00 UTC

[jira] [Commented] (MESOS-8377) RecoverTest.CatchupTruncated is flaky.

    [ https://issues.apache.org/jira/browse/MESOS-8377?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16311747#comment-16311747 ] 

Jie Yu commented on MESOS-8377:
-------------------------------

commit 39525482a756e951e798db4c6831b79b65bb75b5 (HEAD -> master, origin/master, origin/HEAD)
Author: Ilya Pronin <ip...@twopensource.com>
Date:   Thu Jan 4 09:51:05 2018 -0800

    Fixed RecoverTest.CatchupTruncated test flakiness.

    Most likely the "lock already held by process" LevelDB error was caused
    by a Shared<Replica> still retained by one of the processes when the
    test tries to recreate it. This change makes sure that the test code is
    the only owner of the replica.

    Review: https://reviews.apache.org/r/64938/

> RecoverTest.CatchupTruncated is flaky.
> --------------------------------------
>
>                 Key: MESOS-8377
>                 URL: https://issues.apache.org/jira/browse/MESOS-8377
>             Project: Mesos
>          Issue Type: Bug
>          Components: replicated log
>            Reporter: Alexander Rukletsov
>            Assignee: Ilya Pronin
>              Labels: flaky-test
>             Fix For: 1.5.0
>
>         Attachments: CatchupTruncated-badrun.txt, RecoverTest.CatchupTruncated-badrun2.txt
>
>
> Observing regularly in our CI. Logs attached.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)