[ https://issues.apache.org/jira/browse/DL-155?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Liang Xie updated DL-155: ------------------------- Affects Version/s: 0.4.0 > 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)