[
https://issues.apache.org/jira/browse/ZOOKEEPER-3046?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16498640#comment-16498640
]
Michael Han commented on ZOOKEEPER-3046:
----------------------------------------
{quote} any chance this is a deadlock? {quote}
Possible, if for some reasons the current expected packet never arrives at
client side, we will wait forever (current Java client library does not used
timed wait while finishing a packet).
The symptom here sounds similar as what's reported by many users in
ZOOKEEPER-2251. Note in that issue, we still don't figure out what is the real
cause of the (so called "packet loss" - which not might be a precise term, see
[~suda]'s comment and analysis in that issue). It seems this test case can lead
to such "packet loss" in high probability. I feel what this test case and user
stories in ZOOKEEPER-2251 is correlated to a real bug hidden somewhere in our
client library.
> testManyChildWatchersAutoReset is flaky
> ---------------------------------------
>
> Key: ZOOKEEPER-3046
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-3046
> Project: ZooKeeper
> Issue Type: Bug
> Components: tests
> Affects Versions: 3.5.3, 3.4.12
> Reporter: Bogdan Kanivets
> Assignee: Bogdan Kanivets
> Priority: Minor
> Labels: flaky, pull-request-available
> Fix For: 3.6.0, 3.4.13, 3.5.5
>
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> According to the
> [dashboard|https://builds.apache.org/job/ZooKeeper-Find-Flaky-Tests/lastSuccessfulBuild/artifact/report.html]
> Â testManyChildWatchersAutoReset is flaky in 3.4 and 3.5
> [ZooKeeper_branch34_java10|https://builds.apache.org/job/ZooKeeper_branch34_java10//13]
> [ZooKeeper_branch35_java9|https://builds.apache.org/job/ZooKeeper_branch35_java9/253]
> Test times out and because of that ant doesn't capture any output.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
