Return-Path: X-Original-To: apmail-hadoop-common-issues-archive@minotaur.apache.org Delivered-To: apmail-hadoop-common-issues-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id C8715108DA for ; Thu, 12 Dec 2013 16:11:14 +0000 (UTC) Received: (qmail 68089 invoked by uid 500); 12 Dec 2013 16:11:11 -0000 Delivered-To: apmail-hadoop-common-issues-archive@hadoop.apache.org Received: (qmail 68079 invoked by uid 500); 12 Dec 2013 16:11:11 -0000 Mailing-List: contact common-issues-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: common-issues@hadoop.apache.org Delivered-To: mailing list common-issues@hadoop.apache.org Received: (qmail 68055 invoked by uid 99); 12 Dec 2013 16:11:10 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 12 Dec 2013 16:11:10 +0000 Date: Thu, 12 Dec 2013 16:11:10 +0000 (UTC) From: "Jonathan Eagles (JIRA)" To: common-issues@hadoop.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Updated] (HADOOP-10162) BACKPORT HADOOP-10052 to Branch-2 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/HADOOP-10162?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jonathan Eagles updated HADOOP-10162: ------------------------------------- Assignee: Mit Desai (was: Jonathan Eagles) > BACKPORT HADOOP-10052 to Branch-2 > --------------------------------- > > Key: HADOOP-10162 > URL: https://issues.apache.org/jira/browse/HADOOP-10162 > Project: Hadoop Common > Issue Type: Bug > Affects Versions: 2.4.0 > Reporter: Mit Desai > Assignee: Mit Desai > > We need to backport HADOOP-10052 to branch-2 as I found that the TestFileContextResolveAfs is failing after HADOOP-10020 went in. > Also the test TestStat is failing for the same reason. It needs to be fixed as well. -- This message was sent by Atlassian JIRA (v6.1.4#6159)