[
https://issues.apache.org/jira/browse/HBASE-4438?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13112816#comment-13112816
]
Jesse Yates commented on HBASE-4438:
------------------------------------
Right now its not too hard to get the integration tests named differently to
run in a separate phase (basically add in the failsafe plugin and rename them
all to **/IT*.java, or whatever regex we want). However with the split proposed
in HBASE-4336, everything is going to move around anyways, so we might as well
just get it done all together.
Granted there is going to be some serious pain when we break out into modules.
Adding ticket (HBASE-4454) so we can just do the integration tests with naming,
for the moment.
> 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