[
https://issues.apache.org/jira/browse/HBASE-14725?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14981822#comment-14981822
]
Sean Busbey commented on HBASE-14725:
-------------------------------------
no joy. Anywho, if you update top level pom:
{code}
diff --git a/pom.xml b/pom.xml
index 5bcdbc5..b69360d 100644
--- a/pom.xml
+++ b/pom.xml
@@ -567,6 +567,7 @@
<failIfNoTests>false</failIfNoTests>
<skip>${surefire.skipFirstPart}</skip>
<forkCount>${surefire.firstPartForkCount}</forkCount>
+ <groups>${surefire.firstPartGroups}</groups>
<reuseForks>false</reuseForks>
<testFailureIgnore>${surefire.testFailureIgnore}</testFailureIgnore>
<forkedProcessTimeoutInSeconds>${surefire.timeout}</forkedProcessTimeoutInSeconds>
{code}
then you can remove similar configs in individual modules. It used to be that
we couldn't set it at the top level because then none of the hadoop-compat
tests would run, but those are categorized as of HBASE-14516
> Vet categorization of tests so they for sure go into the right
> small/medium/large buckets
> -----------------------------------------------------------------------------------------
>
> Key: HBASE-14725
> URL: https://issues.apache.org/jira/browse/HBASE-14725
> Project: HBase
> Issue Type: Sub-task
> Components: test
> Reporter: stack
> Attachments: categorization.patch
>
>
> I tried doing runSmallTests, runMediumTests, etc., and I noticed that some
> tests are larger than our categorization. At least for small tests it means
> they area all running in the one JVM. I also noticed that the categorization
> only takes effect in hbase-server.
> This patch makes it so runSmallTests runs all the small tests only in each
> category. Also moves tests that were larger than small out to medium so they
> don't run in the one JVM anymore.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
