Mailing-List: contact issues-help@hbase.apache.org; run by ezmlm
Precedence: bulk
Date: Tue, 20 Sep 2011 05:26:08 +0000 (UTC)
From: "Jesse Yates (JIRA)" <jira@apache.org>
To: issues@hbase.apache.org
Message-ID: 
 <986350018.44950.1316496368895.JavaMail.tomcat@hel.zones.apache.org>
In-Reply-To: 
 <354720470.42919.1316452148806.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Commented] (HBASE-4438) Speed the build test phase
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/HBASE-4438?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13108379#comment-13108379 ] 

Jesse Yates commented on HBASE-4438:
------------------------------------

And by "here" I mean HBASE-4336.

> Speed the build test phase
> --------------------------
>
>                 Key: HBASE-4438
>                 URL: https://issues.apache.org/jira/browse/HBASE-4438
>             Project: HBase
>          Issue Type: Umbrella
>          Components: test
>            Reporter: stack
>
> We're up to 2hrs 15mins running tests on jenkins which is kinda crazy.  Akash started a thread over in dev on fixing this: http://search-hadoop.com/m/cZjDH1ykGIA/Running+UnitTests+before+submitting+a+patch&subj=Running+UnitTests+before+submitting+a+patch
> Jessie brings up http://maven.apache.org/plugins/maven-failsafe-plugin/ which looks like something we need to start using; having a tiering of our testing would make sense to me.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira