[jira] [Commented] (ZOOKEEPER-1557) jenkins jdk7 test failure in testBadSaslAuthNotifiesWatch

["Flavio Junqueira (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/ZOOKEEPER-1557?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13756522#comment-13756522 ] 

Flavio Junqueira commented on ZOOKEEPER-1557:
---------------------------------------------

I checked the zookeeper-trunk-jdk7 build and it hasn't run since June, which is strange. Before June, the builds that failed were due to this test:

{noformat}
org.apache.zookeeper.server.TruncateCorruptionTest.testTransactionLogCorruption
{noformat}

I don't think we have observed this problem since the last comments from [~phunt], [~mahadev], and [~ekoontz] late last year, so I wonder if this is still an issue. I don't want to hold 3.4.6 because of this issue, so if there is no reason or interest in pursuing it further, I'd like to push it to 3.5.0 or simply resolve it for now. This issue is not blocking 3.4.6 quite yet, but I'm trying to get to a resolution for all issues marked for 3.4.6.
                
> 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