[
https://issues.apache.org/jira/browse/ZOOKEEPER-1557?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13471403#comment-13471403
]
Mahadev konar edited comment on ZOOKEEPER-1557 at 10/8/12 5:04 AM:
-------------------------------------------------------------------
Thanks Eugene for taking a look at it. Given your analysis above it doesnt look
like we have a full knowledge of whats causing the issue. Given that this is
not SASL related and could be related to how our test framework runs, I think
we can move this out to 3.4.6 and get 3.4.5 out the door with what we have now.
What do you think?
was (Author: mahadev):
Thanks Eugene for taking a look at it. Given your any analysis above it
doesnt look like we have a full knowledge of whats causing the issue. Given
that this is not SASL related and could be related to how our test framework
runs, I think we can move this out to 3.4.6 and get 3.4.5 out the door with
what we have now. What do you think?
> jenkins jdk7 test failure in testBadSaslAuthNotifiesWatch
> ---------------------------------------------------------
>
> Key: ZOOKEEPER-1557
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-1557
> Project: ZooKeeper
> Issue Type: Bug
> Components: server
> Affects Versions: 3.5.0, 3.4.5
> Reporter: Patrick Hunt
> Assignee: Eugene Koontz
> Fix For: 3.5.0, 3.4.6
>
> Attachments: jstack.out, SaslAuthFailTest.log, ZOOKEEPER-1557.patch
>
>
> Failure of testBadSaslAuthNotifiesWatch on the jenkins jdk7 job:
> https://builds.apache.org/job/ZooKeeper-trunk-jdk7/407/
> haven't seen this before.
--
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
