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 8BED3FBD9 for ; Fri, 29 Mar 2013 17:21:18 +0000 (UTC) Received: (qmail 15339 invoked by uid 500); 29 Mar 2013 17:21:18 -0000 Delivered-To: apmail-hbase-issues-archive@hbase.apache.org Received: (qmail 15270 invoked by uid 500); 29 Mar 2013 17:21:18 -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 15248 invoked by uid 99); 29 Mar 2013 17:21:17 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 29 Mar 2013 17:21:17 +0000 Date: Fri, 29 Mar 2013 17:21:17 +0000 (UTC) From: "Ted Yu (JIRA)" To: issues@hbase.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Updated] (HBASE-8164) TestTableLockManager fails intermittently in trunk builds MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/HBASE-8164?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ted Yu updated HBASE-8164: -------------------------- Attachment: 8164-addendum.txt > TestTableLockManager fails intermittently in trunk builds > --------------------------------------------------------- > > Key: HBASE-8164 > URL: https://issues.apache.org/jira/browse/HBASE-8164 > Project: HBase > Issue Type: Bug > Reporter: Ted Yu > Assignee: Ted Yu > Fix For: 0.95.0, 0.98.0 > > Attachments: 8164-addendum.txt, 8164-v2.txt, 8164-v3.txt, 8164-v4.txt > > > In build #3979: > testTableReadLock(org.apache.hadoop.hbase.master.TestTableLockManager): test timed out after 600000 milliseconds -- 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