Return-Path: X-Original-To: apmail-hbase-issues-archive@www.apache.org Delivered-To: apmail-hbase-issues-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 28410D834 for ; Sat, 4 Aug 2012 05:28:04 +0000 (UTC) Received: (qmail 245 invoked by uid 500); 4 Aug 2012 05:28:04 -0000 Delivered-To: apmail-hbase-issues-archive@hbase.apache.org Received: (qmail 99950 invoked by uid 500); 4 Aug 2012 05:28:03 -0000 Mailing-List: contact issues-help@hbase.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Delivered-To: mailing list issues@hbase.apache.org Received: (qmail 99933 invoked by uid 99); 4 Aug 2012 05:28:02 -0000 Received: from issues-vm.apache.org (HELO issues-vm) (140.211.11.160) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 04 Aug 2012 05:28:02 +0000 Received: from isssues-vm.apache.org (localhost [127.0.0.1]) by issues-vm (Postfix) with ESMTP id 5CF8614284D for ; Sat, 4 Aug 2012 05:28:02 +0000 (UTC) Date: Sat, 4 Aug 2012 05:28:02 +0000 (UTC) From: "Hadoop QA (JIRA)" To: issues@hbase.apache.org Message-ID: <846223840.13105.1344058082382.JavaMail.jiratomcat@issues-vm> In-Reply-To: <703442604.12370.1344032763649.JavaMail.jiratomcat@issues-vm> Subject: [jira] [Commented] (HBASE-6510) Fix HConnection typo in TestFromClientSide MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/HBASE-6510?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13428564#comment-13428564 ] Hadoop QA commented on HBASE-6510: ---------------------------------- -1 overall. Here are the results of testing the latest attachment http://issues.apache.org/jira/secure/attachment/12539106/HBASE-6510.patch against trunk revision . +1 @author. The patch does not contain any @author tags. +1 tests included. The patch appears to include 3 new or modified tests. +1 hadoop2.0. The patch compiles against the hadoop 2.0 profile. +1 javadoc. The javadoc tool did not generate any warning messages. -1 javac. The applied patch generated 5 javac compiler warnings (more than the trunk's current 4 warnings). -1 findbugs. The patch appears to introduce 10 new Findbugs (version 1.3.9) warnings. +1 release audit. The applied patch does not increase the total number of release audit warnings. -1 core tests. The patch failed these unit tests: org.apache.hadoop.hbase.coprocessor.TestRowProcessorEndpoint org.apache.hadoop.hbase.coprocessor.TestClassLoading org.apache.hadoop.hbase.master.TestSplitLogManager Test results: https://builds.apache.org/job/PreCommit-HBASE-Build/2503//testReport/ Findbugs warnings: https://builds.apache.org/job/PreCommit-HBASE-Build/2503//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-hadoop2-compat.html Findbugs warnings: https://builds.apache.org/job/PreCommit-HBASE-Build/2503//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-hadoop1-compat.html Findbugs warnings: https://builds.apache.org/job/PreCommit-HBASE-Build/2503//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-common.html Findbugs warnings: https://builds.apache.org/job/PreCommit-HBASE-Build/2503//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-hadoop-compat.html Findbugs warnings: https://builds.apache.org/job/PreCommit-HBASE-Build/2503//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-server.html Console output: https://builds.apache.org/job/PreCommit-HBASE-Build/2503//console This message is automatically generated. > Fix HConnection typo in TestFromClientSide > ------------------------------------------ > > Key: HBASE-6510 > URL: https://issues.apache.org/jira/browse/HBASE-6510 > Project: HBase > Issue Type: Bug > Components: test > Reporter: Gregory Chanan > Assignee: Gregory Chanan > Priority: Trivial > Labels: noob > Fix For: 0.96.0 > > Attachments: HBASE-6510.patch > > > {code} > * API that accept a pre-created HConnction instance > {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira