From common-issues-return-57570-apmail-hadoop-common-issues-archive=hadoop.apache.org@hadoop.apache.org Tue Feb 4 00:13:16 2014 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 7432F105EE for ; Tue, 4 Feb 2014 00:13:16 +0000 (UTC) Received: (qmail 31021 invoked by uid 500); 4 Feb 2014 00:13:12 -0000 Delivered-To: apmail-hadoop-common-issues-archive@hadoop.apache.org Received: (qmail 30898 invoked by uid 500); 4 Feb 2014 00:13: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 30773 invoked by uid 99); 4 Feb 2014 00:13:09 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 04 Feb 2014 00:13:09 +0000 Date: Tue, 4 Feb 2014 00:13:09 +0000 (UTC) From: "Owen O'Malley (JIRA)" To: common-issues@hadoop.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Updated] (HADOOP-10244) TestKeyShell improperly tests the results of a Delete 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-10244?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Owen O'Malley updated HADOOP-10244: ----------------------------------- Resolution: Fixed Fix Version/s: 3.0.0 Status: Resolved (was: Patch Available) I just committed this. Thanks, Larry! > TestKeyShell improperly tests the results of a Delete > ----------------------------------------------------- > > Key: HADOOP-10244 > URL: https://issues.apache.org/jira/browse/HADOOP-10244 > Project: Hadoop Common > Issue Type: Bug > Components: security > Reporter: Larry McCay > Assignee: Larry McCay > Fix For: 3.0.0 > > Attachments: 10244.patch > > > The TestKeyShell.testKeySuccessfulKeyLifecycle test is supposed to ensure that the deleted key is no longer in the results of a subsequent delete command. Mistakenly, it is testing that it is STILL there. > The delete command is actually working but the stdout capture should be reset instead of flushed. Therefore, the test is picking up the existence of the key name from the deletion message in the previous command. -- This message was sent by Atlassian JIRA (v6.1.5#6160)