You are viewing a plain text version of this content. The canonical link for it is here.

Posted to common-issues@hadoop.apache.org by "Larry McCay (JIRA)" <ji...@apache.org> on 2014/01/20 21:35:20 UTC

[jira] [Updated] (HADOOP-10244) TestKeyShell improperly tests the results of a Delete

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

Larry McCay updated HADOOP-10244:
---------------------------------

    Release Note: Fix of inappropriate test of delete functionality.
          Status: Patch Available  (was: Open)

Fix of inappropriate test of delete functionality. Changed the use of flush to reset and test that the deleted keyName is expected to NOT be in the list output after a delete.

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