You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "stack (JIRA)" <ji...@apache.org> on 2016/03/02 17:45:18 UTC
[jira] [Resolved] (HBASE-14356) Add parent timeout rule to all unit
tests
[ https://issues.apache.org/jira/browse/HBASE-14356?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
stack resolved HBASE-14356.
---------------------------
Resolution: Won't Fix
Stepping down. I've been adding categorybased timeouts as I go rather than in one grand gesture as this issue would have it.
Missing timeouts are for the most part no longer a problem -- we don't have tests that fail because they timeout anymore.. Problematic tests either have explicit or category-based timeouts.
I was going to do a write up on how to write a unit test.... that would include adding category-based timeout... TODO.
> Add parent timeout rule to all unit tests
> -----------------------------------------
>
> Key: HBASE-14356
> URL: https://issues.apache.org/jira/browse/HBASE-14356
> Project: HBase
> Issue Type: Improvement
> Components: test
> Reporter: stack
> Assignee: stack
> Priority: Critical
> Fix For: 2.0.0, 1.3.0, 1.2.1, 1.1.4, 1.0.2
>
>
> Parent issue added a timeout rule. The rule needs to be mentioned in all tests to take effect. Add it.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)