You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@hbase.apache.org by "stack (JIRA)" <ji...@apache.org> on 2017/01/26 20:00:29 UTC

[jira] [Reopened] (HBASE-16785) We are not running all tests

     [ https://issues.apache.org/jira/browse/HBASE-16785?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

stack reopened HBASE-16785:
---------------------------

> 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
>
>
> 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)