distributedlog-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (DL-155) TestAsyncReaderLock#testReaderLockMultiReadersScenario is flaky
Date Thu, 22 Dec 2016 08:54:58 GMT

    [ https://issues.apache.org/jira/browse/DL-155?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15769519#comment-15769519

ASF GitHub Bot commented on DL-155:

GitHub user xieliang opened a pull request:


    DL-155 : fix flaky TestAsyncReaderLock#testReaderLockMultiReadersScenario

    Ran the case with changed patch 30 times, all are passed;   and it'll fail w/o patch

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/xieliang/incubator-distributedlog DL-155

Alternatively you can review and apply these changes as the patch at:


To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #88
commit 44d273afde6d04aa35464170bec770b578c92e4b
Author: xieliang <xieliang007@gmail.com>
Date:   2016-12-22T08:46:25Z

    fix flaky TestAsyncReaderLock#testReaderLockMultiReadersScenario


> TestAsyncReaderLock#testReaderLockMultiReadersScenario is flaky
> ---------------------------------------------------------------
>                 Key: DL-155
>                 URL: https://issues.apache.org/jira/browse/DL-155
>             Project: DistributedLog
>          Issue Type: Bug
>          Components: distributedlog-core
>    Affects Versions: 0.4.0
>            Reporter: Liang Xie
>            Assignee: Liang Xie
> See https://builds.apache.org/job/distributedlog-nightly-build/com.twitter$distributedlog-core/162/testReport/junit/com.twitter.distributedlog/TestAsyncReaderLock/testReaderLockMultiReadersScenario/
> The error  came from write path, due to extra control records be transmitted sometimes,
the entryId probably more than 99 which was expected in original case.
> DL-151 had a similar issue and gave a solution already.

This message was sent by Atlassian JIRA

View raw message