hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "stack (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (HBASE-16785) We are not running all tests
Date Fri, 27 Jan 2017 05:55:25 GMT

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

stack updated HBASE-16785:
       Resolution: Fixed
     Hadoop Flags: Reviewed
    Fix Version/s: 2.0.0
           Status: Resolved  (was: Patch Available)

Pushed to master branch.

> 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
>             Fix For: 2.0.0
>         Attachments: HBASE-16785.master.001.patch, HBASE-16785.master.002 (1).patch,
HBASE-16785.master.002 (2).patch, HBASE-16785.master.002 (2).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

View raw message