hbase-issues mailing list archives

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

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

stack commented on HBASE-4438:

Regards 'Option 2', the break-up of hbase into modules is going to happen in TRUNK for other
reasons so you can assume submodules a non-obstacle -- for TRUNK; modules will not happen
for 0.92 branch.

On integration tests, going by Todd definition, we need to do those too.  On "long-running
functional tests", yes would be grand to break them apart.  I'd be fine with renaming long
tests with *LongRunningFunctionalTest suffix or some such so we could distinguish them before
a SUREFIRE-329 shows up (On SUREFIRE-329, Todd, you get around).

> 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


View raw message