Mailing-List: contact dev-help@hive.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@hive.apache.org
Date: Sat, 26 Jan 2013 02:49:13 +0000 (UTC)
From: "Phabricator (JIRA)" <jira@apache.org>
To: hive-dev@hadoop.apache.org
Message-ID: <JIRA.12629370.1359168448214.194693.1359168553687@arcas>
In-Reply-To: <JIRA.12629370.1359168448214@arcas>
References: <JIRA.12629370.1359168448214@arcas>
Subject: [jira] [Updated] (HIVE-3947) MiniMR test remains pening after test
 completion
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/HIVE-3947?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Phabricator updated HIVE-3947:
------------------------------

    Attachment: HIVE-3947.D8205.1.patch

navis requested code review of "HIVE-3947 [jira] MiniMR test remains pening after test completion".
Reviewers: JIRA

  DPAL-1972 MiniMR test remains pening after test completion

  Shutdown hook tries delete "delete on exit" files after test completion but it cannot because HDFS is closed already.

TEST PLAN
  EMPTY

REVISION DETAIL
  https://reviews.facebook.net/D8205

AFFECTED FILES
  ql/src/test/org/apache/hadoop/hive/ql/QTestUtil.java

MANAGE HERALD DIFFERENTIAL RULES
  https://reviews.facebook.net/herald/view/differential/

WHY DID I GET THIS EMAIL?
  https://reviews.facebook.net/herald/transcript/19827/

To: JIRA, navis

                
> MiniMR test remains pening after test completion
> ------------------------------------------------
>
>                 Key: HIVE-3947
>                 URL: https://issues.apache.org/jira/browse/HIVE-3947
>             Project: Hive
>          Issue Type: Bug
>          Components: Tests
>            Reporter: Navis
>            Assignee: Navis
>            Priority: Trivial
>         Attachments: HIVE-3947.D8205.1.patch
>
>
> Shutdown hook tries delete "delete on exit" files after test completion but it cannot because HDFS is closed already.

--
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