[
https://issues.apache.org/jira/browse/ZOOKEEPER-2282?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15514515#comment-15514515
]
Hadoop QA commented on ZOOKEEPER-2282:
--------------------------------------
-1 overall. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12829924/ZOOKEEPER-2282.patch
against trunk revision ec20c5434cc8a334b3fd25e27d26dccf4793c8f3.
+1 @author. The patch does not contain any @author tags.
+1 tests included. The patch appears to include 3 new or modified tests.
+1 javadoc. The javadoc tool did not generate any warning messages.
+1 javac. The applied patch does not increase the total number of javac
compiler warnings.
+1 findbugs. The patch does not introduce any new Findbugs (version 2.0.3)
warnings.
+1 release audit. The applied patch does not increase the total number of
release audit warnings.
-1 core tests. The patch failed core unit tests.
+1 contrib tests. The patch passed contrib unit tests.
Test results:
https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/3450//testReport/
Findbugs warnings:
https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/3450//artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html
Console output:
https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/3450//console
This message is automatically generated.
> chroot not stripped from path in asynchronous callbacks
> -------------------------------------------------------
>
> Key: ZOOKEEPER-2282
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2282
> Project: ZooKeeper
> Issue Type: Bug
> Components: c client
> Affects Versions: 3.4.6, 3.5.0
> Environment: Centos 6.6
> Reporter: Andrew Grasso
> Assignee: Andrew Grasso
> Priority: Critical
> Attachments: ZOOKEEPER-2282.patch
>
> Original Estimate: 1h
> Remaining Estimate: 1h
>
> Callbacks passed to [zoo_acreate], [zoo_async], and [zoo_amulti] (for create
> ops) are called on paths that include the chroot. This is analagous to issue
> 1027, which fixed this bug for synchronous calls.
> I've created a patch to fix this in trunk
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
