[
https://issues.apache.org/jira/browse/ZOOKEEPER-3193?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16700321#comment-16700321
]
Hudson commented on ZOOKEEPER-3193:
-----------------------------------
SUCCESS: Integrated in Jenkins build Zookeeper-trunk-single-thread #123 (See
[https://builds.apache.org/job/Zookeeper-trunk-single-thread/123/])
ZOOKEEPER-3193: Flaky: org.apache.zookeeper.test.SaslAuthFailNotifyTest (andor:
rev 1c488cec08809a76202f6c66be9e46533e7c409c)
* (edit)
zookeeper-server/src/test/java/org/apache/zookeeper/test/SaslAuthFailTest.java
* (delete)
zookeeper-server/src/test/java/org/apache/zookeeper/test/SaslAuthFailNotifyTest.java
> Flaky: org.apache.zookeeper.test.SaslAuthFailNotifyTest
> -------------------------------------------------------
>
> Key: ZOOKEEPER-3193
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-3193
> Project: ZooKeeper
> Issue Type: Sub-task
> Components: tests
> Affects Versions: 3.5.4, 3.6.0, 3.4.13
> Reporter: Andor Molnar
> Assignee: Andor Molnar
> Priority: Major
> Labels: pull-request-available
> Fix For: 3.6.0, 3.5.5
>
> Time Spent: 40m
> Remaining Estimate: 0h
>
> This test doesn't fail often on Apache Jenkins, but seems like quite flaky in
> our in-house testing environment. It's having a race in waiting for the
> AuthFailed event that could happen before client creation succeeds, causing
> the wait operation to hand infinitely (notify occurred before the wait()
> call). Using a CountDownLatch would be better for the same purpose.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
