[ https://issues.apache.org/jira/browse/ZOOKEEPER-2276?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15518642#comment-15518642 ]
Hadoop QA commented on ZOOKEEPER-2276: -------------------------------------- -1 overall. Here are the results of testing the latest attachment http://issues.apache.org/jira/secure/attachment/12830178/ZOOKEEPER-2276-02.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/3451//testReport/ Findbugs warnings: https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/3451//artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html Console output: https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/3451//console This message is automatically generated. > Multi operation failure does not include path in KeeperException > ----------------------------------------------------------------- > > Key: ZOOKEEPER-2276 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2276 > Project: ZooKeeper > Issue Type: Bug > Components: java client > Affects Versions: 3.5.0 > Environment: Suse 11 SP3 > Reporter: neha > Assignee: Arshad Mohammad > Priority: Minor > Fix For: 3.5.3 > > Attachments: ZOOKEEPER-2276-01.patch, ZOOKEEPER-2276-02.patch > > > With normal create operation, the path of the failed node is displayed in > KeeperException but this is not the case when create operation is through > multi api -- This message was sent by Atlassian JIRA (v6.3.4#6332)