[
https://issues.apache.org/jira/browse/ZOOKEEPER-1629?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13707911#comment-13707911
]
Alexander Shraer commented on ZOOKEEPER-1629:
---------------------------------------------
The attached patch disables testTransactionLogCorruption, and includes a minor
fix to TruncateTest (specifies leader election and client ports).
As explained above the logic of testTransactionLogCorruption is problematic.
But it was introduced in ZOOKEEPER-1489 to solve some problem, so I wanted to
make sure we're still covering that problem. ZOOKEEPER-1489 makes changes to
two functions. Reverting either of these changes causes one of the tests in
TruncateTest to fail. On the other hand, reverting the ZOOKEEPER-1489 changes
doesn't cause testTransactionLogCorruption to fail. Even more reason to disable
it.
Alex
> 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,
> ZOOKEEPER-1629-ver1.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
