[
https://issues.apache.org/jira/browse/ZOOKEEPER-1629?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13619031#comment-13619031
]
Alexander Shraer commented on ZOOKEEPER-1629:
---------------------------------------------
Hi Ben,
The test was added here: https://issues.apache.org/jira/browse/ZOOKEEPER-1489,
and there are some explanations on what it does on that jira.
I think I more or less understand what it tried to do, but whoever wrote it
should probably explain it.
In my opinion, besides small bugs which are the ones causing our periodic
builds to fail, the test just doesn't take snapshots into account and
this results in the failure we're seeing in the pre-commit build (see my
previous comment above). We should probably disable the test until it is fixed.
> 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
> 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
