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-171) TestAppendOnlyStreamWriter#testPositionUpdatesOnlyAfterWriteCompletionWithoutFsync failed occasionally
Date Sat, 07 Jan 2017 07:39:58 GMT

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

Hudson commented on DL-171:

UNSTABLE: Integrated in Jenkins build distributedlog-nightly-build #181 (See [https://builds.apache.org/job/distributedlog-nightly-build/181/])
DL-171: adding a short sleep to let the WriteCompleteListener have time (sijieg: rev 859b342b25dcac3cf4c2353c2d2ff4994d4bcaba)
* (edit) distributedlog-core/src/test/java/org/apache/distributedlog/TestAppendOnlyStreamWriter.java

> TestAppendOnlyStreamWriter#testPositionUpdatesOnlyAfterWriteCompletionWithoutFsync failed
> ------------------------------------------------------------------------------------------------------
>                 Key: DL-171
>                 URL: https://issues.apache.org/jira/browse/DL-171
>             Project: DistributedLog
>          Issue Type: Bug
>          Components: tests
>    Affects Versions: 0.4.0
>            Reporter: Liang Xie
>            Assignee: Liang Xie
>             Fix For: 0.4.0
> I had seen several failed running, i.g. the latest one: https://builds.apache.org/job/distributedlog-precommit-pullrequest/68/com.twitter$distributedlog-core/testReport/com.twitter.distributedlog/TestAppendOnlyStreamWriter/testPositionUpdatesOnlyAfterWriteCompletionWithoutFsync/
> I can reproduce it after several runnings locally, after diving into the detail, it turn
out that an execution sequence issue: once the "writer.write" be done, if "writer.position()"
be invoked easier than the WriteCompleteListener onSuccess callback,  due to the "synchronized",
the position result will be 0, not the expected 33. we can just add a short sleep to avoid
this test issue.

This message was sent by Atlassian JIRA

View raw message