You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@zookeeper.apache.org by "ASF GitHub Bot (JIRA)" <ji...@apache.org> on 2018/11/19 16:27:01 UTC
[jira] [Updated] (ZOOKEEPER-3193) Flaky:
org.apache.zookeeper.test.SaslAuthFailNotifyTest
[ https://issues.apache.org/jira/browse/ZOOKEEPER-3193?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
ASF GitHub Bot updated ZOOKEEPER-3193:
--------------------------------------
Labels: pull-request-available (was: )
> 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, 3.4.14
>
>
> 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)