You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Hadoop QA (JIRA)" <ji...@apache.org> on 2013/08/07 11:04:50 UTC
[jira] [Commented] (HBASE-9146) TestHTablePool hangs when run as
part of runMediumTests profile
[ https://issues.apache.org/jira/browse/HBASE-9146?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13731793#comment-13731793 ]
Hadoop QA commented on HBASE-9146:
----------------------------------
{color:red}-1 overall{color}. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12596519/Waiting%20threads%20%28TestHTablePool%29%20-%20%20HBase%20medium%20tests
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author tags.
{color:red}-1 tests included{color}. The patch doesn't appear to include any new or modified tests.
Please justify why no new tests are needed for this patch.
Also please list what manual steps were performed to verify this patch.
{color:red}-1 patch{color}. The patch command could not apply the patch.
Console output: https://builds.apache.org/job/PreCommit-HBASE-Build/6628//console
This message is automatically generated.
> 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: 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 TestHTablePool contains a class TestHTablePoolType which uses nested static test classes. But the initialization is being done for the outer class - TestHTablePool 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 setUpBeforeClass() is not being called and hence the initialization is not done.
> Guess that surefire tries to run TestHTablePool.TestHTableReusablePool.class directly. (Tried this by writing a separate program using JUnitCore.runClasses(TTestHTablePool.TestHTableReusablePool.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