hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Rajesh Venkatachalam (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-9146) TestHTablePool hangs when run as part of runMediumTests profile
Date Wed, 07 Aug 2013 18:39:48 GMT

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

Rajesh Venkatachalam commented on HBASE-9146:
---------------------------------------------

Hi Ramkrishna. Surefire runs the same test (TestHTableReusablePool) twice. This happens if
you run with 'runMediumTests' profile.  I don't know the exact reason for this. But in one
of such runs, the cluster is not getting started. 

This test passes in the jenkins build. But it fails locally if you run the medium tests alone.
The problem seems to be due to surefire, but this fix in the test will prevent this failure.

                
> TestHTablePool hangs when run as part of runMediumTests profile
> ---------------------------------------------------------------
>
>                 Key: HBASE-9146
>                 URL: https://issues.apache.org/jira/browse/HBASE-9146
>             Project: HBase
>          Issue Type: Bug
>          Components: test
>            Reporter: Rajesh Venkatachalam
>              Labels: test
>         Attachments: TestHTablePool.java.patch, Waiting threads (TestHTablePool) -  HBase
medium tests
>
>
> In the medium set, we found a test -'TestHTablePool.java' hanging and the build fails
reporting a timeout. Though the test passes when run separately, while running the whole suite
using the command " mvn -U clean package -Dhadoop.profile=2.0  -Psecurity -Dsnappy -P runMediumTests",
this test is observed in a waiting state, tracking for the root region server.
> It turns out be a problem with the test initialization. The class TestHTable​Pool contains
a class TestHTable​PoolType which uses nested static test classes. But the initializati​on
is being done for the outer class - TestHTable​Pool using @BeforeClass annotation. Surefire
reruns the tests written in nested manner (for some reasons), and when this test is instantiated
the second time, the method setUpBefore​Class() is not being called and hence the initializati​on
is not done.
> Guess that surefire tries to run TestHTable​Pool.​TestHTable​ReusablePool.​class
directly. (Tried this by writing a separate program using JUnitCore.​runClasses(​TTestHTable​Pool.​TestHTable​ReusablePool.​class)
and observed that the outer class's @BeforeClass method is not called.)

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message