distributedlog-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hudson (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (DL-155) TestAsyncReaderLock#testReaderLockMultiReadersScenario is flaky
Date Wed, 28 Dec 2016 07:33:59 GMT

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

Hudson commented on DL-155:
---------------------------

UNSTABLE: Integrated in Jenkins build distributedlog-nightly-build #170 (See [https://builds.apache.org/job/distributedlog-nightly-build/170/])
DL-155: fix flaky TestAsyncReaderLock#testReaderLockMultiReadersScenario (sijieg: rev cf9bcd2a89bd87ecdc7e2b803ad3f16bdaea61ea)
* (edit) distributedlog-core/src/test/java/com/twitter/distributedlog/TestAsyncReaderLock.java


> 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
(v6.3.4#6332)

Mime
View raw message