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 291F4D33D for ; Fri, 31 Aug 2012 00:25:08 +0000 (UTC) Received: (qmail 31610 invoked by uid 500); 31 Aug 2012 00:25:08 -0000 Delivered-To: apmail-hbase-issues-archive@hbase.apache.org Received: (qmail 31576 invoked by uid 500); 31 Aug 2012 00:25:07 -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 31567 invoked by uid 99); 31 Aug 2012 00:25:07 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 31 Aug 2012 00:25:07 +0000 Date: Fri, 31 Aug 2012 11:25:07 +1100 (NCT) From: "Hadoop QA (JIRA)" To: issues@hbase.apache.org Message-ID: <1112283157.19528.1346372707949.JavaMail.jiratomcat@arcas> In-Reply-To: <1470571875.26868.1340054082698.JavaMail.jiratomcat@issues-vm> Subject: [jira] [Commented] (HBASE-6234) Move simple KeyValue tests to hbase-common module 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-6234?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13445501#comment-13445501 ] Hadoop QA commented on HBASE-6234: ---------------------------------- -1 overall. Here are the results of testing the latest attachment http://issues.apache.org/jira/secure/attachment/12543188/HBASE-6234-v2.patch against trunk revision . +1 @author. The patch does not contain any @author tags. +1 tests included. The patch appears to include 21 new or modified tests. +1 hadoop2.0. The patch compiles against the hadoop 2.0 profile. -1 javadoc. The javadoc tool appears to have generated 110 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 11 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: Test results: https://builds.apache.org/job/PreCommit-HBASE-Build/2743//testReport/ Findbugs warnings: https://builds.apache.org/job/PreCommit-HBASE-Build/2743//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-hadoop2-compat.html Findbugs warnings: https://builds.apache.org/job/PreCommit-HBASE-Build/2743//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-server.html Findbugs warnings: https://builds.apache.org/job/PreCommit-HBASE-Build/2743//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-hadoop1-compat.html Findbugs warnings: https://builds.apache.org/job/PreCommit-HBASE-Build/2743//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-common.html Findbugs warnings: https://builds.apache.org/job/PreCommit-HBASE-Build/2743//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-hadoop-compat.html Console output: https://builds.apache.org/job/PreCommit-HBASE-Build/2743//console This message is automatically generated. > Move simple KeyValue tests to hbase-common module > ------------------------------------------------- > > Key: HBASE-6234 > URL: https://issues.apache.org/jira/browse/HBASE-6234 > Project: HBase > Issue Type: Improvement > Affects Versions: 0.96.0 > Reporter: Matt Corgan > Assignee: Matt Corgan > Attachments: HBASE-6234-v1.patch, HBASE-6234-v2.patch > > > TestKeyValue, LoadTestKVGenerator, and TestLoadTestKVGenerator should move up to hbase-common. This brings MD5Hash up as a dependency as well. > To play well with Maven as discussed in HBASE-6162, I moved LoadTestKVGenerator from the src/test folder to src/main folder so that tests in other modules can see it. A couple other files' import statements were affected by this. -- 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