Return-Path: X-Original-To: apmail-hbase-issues-archive@www.apache.org Delivered-To: apmail-hbase-issues-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id C93D310935 for ; Wed, 7 Aug 2013 09:22:49 +0000 (UTC) Received: (qmail 70026 invoked by uid 500); 7 Aug 2013 09:22:49 -0000 Delivered-To: apmail-hbase-issues-archive@hbase.apache.org Received: (qmail 69693 invoked by uid 500); 7 Aug 2013 09:22:49 -0000 Mailing-List: contact issues-help@hbase.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Delivered-To: mailing list issues@hbase.apache.org Received: (qmail 69659 invoked by uid 99); 7 Aug 2013 09:22:48 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 07 Aug 2013 09:22:48 +0000 Date: Wed, 7 Aug 2013 09:22:48 +0000 (UTC) From: "Rajesh Venkatachalam (JIRA)" To: issues@hbase.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Updated] (HBASE-9146) TestHTablePool hangs when run as part of runMediumTests profile MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/HBASE-9146?page=3Dcom.atlassia= n.jira.plugin.system.issuetabpanels:all-tabpanel ] Rajesh Venkatachalam updated HBASE-9146: ---------------------------------------- Status: Patch Available (was: Open) =20 > 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 (TestHTab= lePool) - 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 separatel= y, while running the whole suite using the command " mvn -U clean package -= Dhadoop.profile=3D2.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 TestHTa= ble=E2=80=8BPool contains a class TestHTable=E2=80=8BPoolType which uses ne= sted static test classes. But the initializati=E2=80=8Bon is being done for= the outer class - TestHTable=E2=80=8BPool using @BeforeClass annotation. S= urefire reruns the tests written in nested manner (for some reasons), and w= hen this test is instantiated the second time, the method setUpBefore=E2=80= =8BClass() is not being called and hence the initializati=E2=80=8Bon is not= done. > Guess that surefire tries to run TestHTable=E2=80=8BPool.=E2=80=8BTestHTa= ble=E2=80=8BReusablePool.=E2=80=8Bclass directly. (Tried this by writing a = separate program using JUnitCore.=E2=80=8BrunClasses(=E2=80=8BTTestHTable= =E2=80=8BPool.=E2=80=8BTestHTable=E2=80=8BReusablePool.=E2=80=8Bclass) 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 administrato= rs For more information on JIRA, see: http://www.atlassian.com/software/jira