[
https://issues.apache.org/jira/browse/HBASE-16785?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
stack updated HBASE-16785:
--------------------------
Status: Patch Available (was: Reopened)
Submit a do-nothing patch just to get benchmark of how many tests are run when
I touch the set of modules that are skipping second part of tests.
> We are not running all tests
> ----------------------------
>
> Key: HBASE-16785
> URL: https://issues.apache.org/jira/browse/HBASE-16785
> Project: HBase
> Issue Type: Bug
> Components: build, test
> Reporter: stack
> Assignee: stack
> Attachments: HBASE-16785.master.001.patch, HBASE-16785.master.002
> (1).patch, HBASE-16785.master.002.patch, HBASE-16785.master.002.patch,
> HBASE-16785.master.003.patch
>
>
> Noticed by [~mbertozzi]
> We have some modules where we tried to 'skip' the running of the second part
> of tests -- medium and larges. That might have made sense once when the
> module was originally added when there may have been just a few small tests
> to run but as time goes by and the module accumulates more tests.... in a few
> cases we've added mediums and larges but we've not removed the 'skip' config.
> Matteo noticed this happened in hbase-procedure.
> In hbase-client, there is at least a medium test that is being skipped.
> Let me try purging this trick everywhere. It doesn't seem to save us anything
> going by build time.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
