Return-Path: X-Original-To: apmail-hbase-dev-archive@www.apache.org Delivered-To: apmail-hbase-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id A66BA1007F for ; Mon, 2 Mar 2015 18:56:05 +0000 (UTC) Received: (qmail 60908 invoked by uid 500); 2 Mar 2015 18:56:04 -0000 Delivered-To: apmail-hbase-dev-archive@hbase.apache.org Received: (qmail 60815 invoked by uid 500); 2 Mar 2015 18:56:04 -0000 Mailing-List: contact dev-help@hbase.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@hbase.apache.org Delivered-To: mailing list dev@hbase.apache.org Received: (qmail 60592 invoked by uid 99); 2 Mar 2015 18:56:04 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 02 Mar 2015 18:56:04 +0000 Date: Mon, 2 Mar 2015 18:56:04 +0000 (UTC) From: "stack (JIRA)" To: dev@hbase.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Resolved] (HBASE-13138) Clean up TestMasterObserver (debug, trying to figure why fails) 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-13138?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] stack resolved HBASE-13138. --------------------------- Resolution: Fixed Fix Version/s: 1.1.0 2.0.0 > Clean up TestMasterObserver (debug, trying to figure why fails) > --------------------------------------------------------------- > > Key: HBASE-13138 > URL: https://issues.apache.org/jira/browse/HBASE-13138 > Project: HBase > Issue Type: Improvement > Components: test > Reporter: stack > Assignee: stack > Fix For: 2.0.0, 1.1.0 > > Attachments: 13138.txt > > > Over w/e, added timeout on TestMasterObserver. Now it no longer zombies but fails with timeout. Looking at log, its full of spew about table disabling. Let me fix the spew so have better chance at seeing why fails. -- This message was sent by Atlassian JIRA (v6.3.4#6332)