[
https://issues.apache.org/jira/browse/HBASE-11911?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
stack updated HBASE-11911:
--------------------------
Attachment: HBASE-11911-v3.patch
Retrying. [~posix4e], can you confirm all tests ran (it relies on
categorization IIRC). There is a section in refguide on test categorization
that would need updating for this to go in. We could do in follow-on?
The small, medium, and large were also factors used figuring whether to run
tests in one jvm, or fork jvm per test. What happens now? Thanks.
> Break up tests into more fine grained categories
> ------------------------------------------------
>
> Key: HBASE-11911
> URL: https://issues.apache.org/jira/browse/HBASE-11911
> Project: HBase
> Issue Type: Sub-task
> Reporter: Alex Newman
> Assignee: Alex Newman
> Attachments: HBASE-11911-preview.patch, HBASE-11911-v0.patch,
> HBASE-11911-v1.patch, HBASE-11911-v2.patch, HBASE-11911-v3.patch,
> HBASE-11911-v3.patch
>
>
> Wouldn't it be nice to run all of the client tests (client and the ones in
> hbase-server) in a single command like.
> mvn test -PrunClientTests
> how about all of the small tests not having to do with mapReduce
> mvn test -PrunSmallTests,!runMapReduceTests
> how about breaking up the build into small pieces so it can be run on travis
> or circle-ci. If that's what you are into, +1 this patch.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
