[
https://issues.apache.org/jira/browse/ZOOKEEPER-1629?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13679334#comment-13679334
]
Alexander Shraer commented on ZOOKEEPER-1629:
---------------------------------------------
I spent some time trying to fix the test today, but no luck so far. I suggest
to disable it.
We can fix the periodic failures by applying the patch attached to the Jira,
but then there are going to be periodic failures of a different kind. The
scenario this test creates is problematic - it deletes the data of 2 servers
and expects the third server to loose committed data. The third server doesn't
loose the data when it succeeds to snapshot it, in which case the test fails. I
tried to delete the snapshot but this creates other problems.
> testTransactionLogCorruption occasionally fails
> -----------------------------------------------
>
> Key: ZOOKEEPER-1629
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-1629
> Project: ZooKeeper
> Issue Type: Bug
> Components: tests
> Reporter: Alexander Shraer
> Assignee: Alexander Shraer
> Fix For: 3.5.0, 3.4.6
>
> Attachments: TruncateCorruptionTest-patch.patch
>
>
> It seems that testTransactionLogCorruption is very flaky,for example fails
> here:
> https://builds.apache.org/job/ZooKeeper-trunk-jdk7/500/
> https://builds.apache.org/job/ZooKeeper-trunk-jdk7/502/
> https://builds.apache.org/job/ZooKeeper-trunk-jdk7/503/#showFailuresLink
> also fails for older builds (no longer on the website), for example all
> builds from 381 to 399.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
