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 D3AC0CB39 for ; Thu, 17 May 2012 22:07:30 +0000 (UTC) Received: (qmail 75215 invoked by uid 500); 17 May 2012 22:07:30 -0000 Delivered-To: apmail-hbase-issues-archive@hbase.apache.org Received: (qmail 75135 invoked by uid 500); 17 May 2012 22:07:30 -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 75105 invoked by uid 99); 17 May 2012 22:07:30 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 17 May 2012 22:07:30 +0000 X-ASF-Spam-Status: No, hits=-2000.0 required=5.0 tests=ALL_TRUSTED,T_RP_MATCHES_RCVD X-Spam-Check-By: apache.org Received: from [140.211.11.116] (HELO hel.zones.apache.org) (140.211.11.116) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 17 May 2012 22:07:29 +0000 Received: from hel.zones.apache.org (hel.zones.apache.org [140.211.11.116]) by hel.zones.apache.org (Postfix) with ESMTP id 4E5A6A2B7 for ; Thu, 17 May 2012 22:07:09 +0000 (UTC) Date: Thu, 17 May 2012 22:07:09 +0000 (UTC) From: "Hadoop QA (JIRA)" To: issues@hbase.apache.org Message-ID: <363661623.11260.1337292429322.JavaMail.tomcat@hel.zones.apache.org> In-Reply-To: <1553746708.24114.1336081850744.JavaMail.tomcat@hel.zones.apache.org> Subject: [jira] [Commented] (HBASE-5932) Move RegionServerStatusProtocol from ipc package to top-level MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 X-Virus-Checked: Checked by ClamAV on apache.org [ https://issues.apache.org/jira/browse/HBASE-5932?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13278324#comment-13278324 ] Hadoop QA commented on HBASE-5932: ---------------------------------- -1 overall. Here are the results of testing the latest attachment http://issues.apache.org/jira/secure/attachment/12527925/HBASE-5932.patch against trunk revision . +1 @author. The patch does not contain any @author tags. -1 tests included. The patch doesn't appear to include any new or modified tests. Please justify why no new tests are needed for this patch. Also please list what manual steps were performed to verify this patch. +1 hadoop23. The patch compiles against the hadoop 0.23.x profile. +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 appears to introduce 32 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.regionserver.TestServerCustomProtocol Test results: https://builds.apache.org/job/PreCommit-HBASE-Build/1919//testReport/ Findbugs warnings: https://builds.apache.org/job/PreCommit-HBASE-Build/1919//artifact/trunk/patchprocess/newPatchFindbugsWarnings.html Console output: https://builds.apache.org/job/PreCommit-HBASE-Build/1919//console This message is automatically generated. > Move RegionServerStatusProtocol from ipc package to top-level > ------------------------------------------------------------- > > Key: HBASE-5932 > URL: https://issues.apache.org/jira/browse/HBASE-5932 > Project: HBase > Issue Type: Task > Affects Versions: 0.96.0 > Reporter: Gregory Chanan > Assignee: Gregory Chanan > Priority: Trivial > Attachments: HBASE-5932.patch > > > From Stack's comment on HBASE-5444: > We can move the ipc protocol stuff to top level later... I was thinking that these classes shared by master and regionservers could be at o.a.h.h... but can do that later if it makes sense. Lets get this pb stuff in first. -- 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