hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Todd Lipcon (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-4438) Speed the build test phase
Date Tue, 20 Sep 2011 03:02:10 GMT

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

Todd Lipcon commented on HBASE-4438:
------------------------------------

My preference is to use JUnit category annotations - with SUREFIRE-329 we can easily separate
long tests from short. Moving tests to separate subdirs seems a little painful to me...

I agree that true integration/system tests should go to a separate dir - but those should
be able to be run against a real cluster without ever accessing daemons directly. We have
many minicluster tests that inject failures, etc, and to call them integration tests is a
bit misleading. Rather they're just "long functional tests".

> 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

        

Mime
View raw message