Mailing-List: contact hadoop-dev-help@lucene.apache.org; run by ezmlm
Precedence: bulk
Reply-To: hadoop-dev@lucene.apache.org
Received-SPF: neutral (herse.apache.org: local policy)
Message-ID: <469E4A9D.40703@duboce.net>
Date: Wed, 18 Jul 2007 10:15:09 -0700
From: Michael Stack <stack@duboce.net>
User-Agent: Thunderbird 1.5.0.12 (Macintosh/20070509)
MIME-Version: 1.0
To: hadoop-dev@lucene.apache.org
Subject: Re: patch process failures
References: <6745EB2F-084C-46C2-AF63-1BB3A4AB4516@yahoo-inc.com>
In-Reply-To: <6745EB2F-084C-46C2-AF63-1BB3A4AB4516@yahoo-inc.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

Thanks for the info below Nigel.  Helps.

Hopefully HADOOP-1616 committed yesterday will make a difference regards 
TestTable sometimes hanging.

But whats is odd is that the two hbase tests cited actually run for a 
short time on my test bench but they do run toward the end of the hbase 
suite.  Could it be that the 15 minutes timeout is for all hbase tests?

Thanks,
St.Ack

Nigel Daley wrote:
> Some of you have asked why the patch process is failing so 
> frequently.  Our unit test suite seems to have destabalized again.
>
> FYI, when you go to a link from the Jira comment like this:
>   
> <http://lucene.zones.apache.org:8080/hudson/job/Hadoop-Patch/430/testReport/> 
>
> and see entries in the "Failed Tests" section like this:
>   org.apache.tools.ant.taskdefs.optional.junit.JUnitTask$1.unknown
> it means that a test took longer than 15 minutes to run and was 
> therefore killed (timeout).
> To find out which one, you have to go to the Console Output ([raw] 
> link) and search for
> FAILED (console output may take a while to load).
>
> I'm seeing TestTable and TestTimestamp timeout most frequently.  Also 
> TestSymLink, TestDecommission, and TestDFSUpgrade fail occasionally.
>
>
> hth,
> Nige