You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@distributedlog.apache.org by "ASF GitHub Bot (JIRA)" <ji...@apache.org> on 2016/12/23 02:47:58 UTC
[jira] [Commented] (DL-155)
TestAsyncReaderLock#testReaderLockMultiReadersScenario is flaky
[ https://issues.apache.org/jira/browse/DL-155?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15771688#comment-15771688 ]
ASF GitHub Bot commented on DL-155:
-----------------------------------
Github user sijie commented on the issue:
https://github.com/apache/incubator-distributedlog/pull/88
The change looks good to me, +1. Thanks @xieliang
> 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)