Mailing-List: contact user-help@hbase.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@hbase.apache.org
Received-SPF: pass (nike.apache.org: domain of yuzhihong@gmail.com designates
 209.85.128.53 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <514B5E95.5010400@linux.vnet.ibm.com>
References: <514B5E95.5010400@linux.vnet.ibm.com>
Date: Thu, 21 Mar 2013 12:46:08 -0700
Message-ID: 
 <CALte62zQ4ViHpTNxm0+GrSVm1p6V_9QMZJFz-LUK9PQ3x8P5SQ@mail.gmail.com>
Subject: Re: Help with identifying test case errors
From: Ted Yu <yuzhihong@gmail.com>
To: user@hbase.apache.org
Content-Type: multipart/alternative; boundary=047d7b6d99a626d3ef04d87497f5

--047d7b6d99a626d3ef04d87497f5
Content-Type: text/plain; charset=ISO-8859-1

I assume you have access to the machine where the tests were run.

Can you use 'jps' command to list the hanging test(s) ?
You would see surefire in process name.

BTW 0.94.3 was a bit old. Can you try with tip of 0.94 or 0.94.6 RC2 ?

Thanks

On Thu, Mar 21, 2013 at 12:25 PM, Aline Guedes
<alinegds@linux.vnet.ibm.com>wrote:

> Hello,
>
> I am running the unit tests for hbase 0.94.3 with maven 3.0.4 using the
> following command:
>
> mvn -Dhadoop.version=1.1.1 -Dzookeeper.version=3.4.5
> -Dtest.timeout=36000000 test -P security,runLargeTests
>
> The build fails, but I don't see clear evidence of test case failures:
>
> Results :
>
> Tests run: 419, Failures: 0, Errors: 0, Skipped: 10
>
> [INFO] ------------------------------**------------------------------**
> ------------
> [INFO] BUILD FAILURE
> [INFO] ------------------------------**------------------------------**
> ------------
> [INFO] Total time: 1:57:19.767s
> [INFO] Finished at: Tue Mar 19 13:13:19 PDT 2013
> [INFO] Final Memory: 36M/512M
> [INFO] ------------------------------**------------------------------**
> ------------
> [ERROR] Failed to execute goal org.apache.maven.plugins:**
> maven-surefire-plugin:2.12-**TRUNK-HBASE-2:test (default-test) on project
> hbase: Failure or timeout ->  [Help 1]
> [ERROR]
>
> Does anyone know how I can figure out what is wrong? I checked for
> evidence that there were test cases hanging (using the same procedure that
> is used in dev-support/findHangingTest.**sh), but it doesn't seem like
> there are any. I think I am missing something.
>
> I appreciate any help you can provide me with.
>
> Thanks,
> Aline
>
>

--047d7b6d99a626d3ef04d87497f5--