[
https://issues.apache.org/jira/browse/HBASE-19873?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16342477#comment-16342477
]
Appy commented on HBASE-19873:
------------------------------
But yeah, get a good QA run, because i suspect that it's a major thing to
change scope of timeout and will likely push a lot of existing tests over new
timeout rule's boundary i.e. many timeout failures.
If it becomes painful to get good run, i'd suggest to first make just the core
change - RunListener and CategoryBasedTimeout - and then addendum/separate
jira for adding rule to tests.
> Add a CategoryBasedTimeout ClassRule for all UTs
> ------------------------------------------------
>
> Key: HBASE-19873
> URL: https://issues.apache.org/jira/browse/HBASE-19873
> Project: HBase
> Issue Type: Sub-task
> Reporter: Duo Zhang
> Assignee: Duo Zhang
> Priority: Major
> Fix For: 2.0.0-beta-2
>
> Attachments: HBASE-19873-v1.patch
>
>
> So that our test can timeout as expected without making the surefire plugin
> kill other tests.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
