[
https://issues.apache.org/jira/browse/HBASE-4438?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
stack updated HBASE-4438:
-------------------------
Component/s: test
Description:
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.
was:
We're up to 2hrs 15mins which is kinda crazy. Akash started a thread over in
dev on fixing it up:
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.
Issue Type: Umbrella (was: Task)
Summary: Speed the build test phase (was: Speed the build)
> 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
