[ 
https://issues.apache.org/jira/browse/HBASE-17004?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15637859#comment-15637859
 ] 

Hudson commented on HBASE-17004:
--------------------------------

SUCCESS: Integrated in Jenkins build HBase-1.2-JDK7 #63 (See 
[https://builds.apache.org/job/HBase-1.2-JDK7/63/])
HBASE-17004  IntegrationTestManyRegions verifies that many regions get (appy: 
rev 804ce850030f607acf855876223d5fa7b3825d0a)
* (edit) 
hbase-it/src/test/java/org/apache/hadoop/hbase/IntegrationTestManyRegions.java
* (edit) hbase-it/pom.xml


> Refactor IntegrationTestManyRegions to use @ClassRule for timing out
> --------------------------------------------------------------------
>
>                 Key: HBASE-17004
>                 URL: https://issues.apache.org/jira/browse/HBASE-17004
>             Project: HBase
>          Issue Type: Improvement
>            Reporter: Appy
>            Assignee: Appy
>            Priority: Minor
>             Fix For: 2.0.0, 1.3.0, 1.4.0, 1.2.4, 1.1.8
>
>         Attachments: HBASE-17004.master.001.patch, 
> HBASE-17004.master.002.patch
>
>
> IntegrationTestManyRegions verifies that many regions get assigned within 
> given time. To do so, it spawns a new thread and uses CountDownLatch.await() 
> to timeout. Replacing this mechanism with junit @ClassRule to timeout the 
> test.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to