[
https://issues.apache.org/jira/browse/HADOOP-10244?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13890225#comment-13890225
]
Hudson commented on HADOOP-10244:
---------------------------------
SUCCESS: Integrated in Hadoop-trunk-Commit #5100 (See
[https://builds.apache.org/job/Hadoop-trunk-Commit/5100/])
HADOOP-10244. TestKeyShell improperly tests the results of delete (Larry
McCay via omalley) (omalley:
http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1564137)
* /hadoop/common/trunk/hadoop-common-project/hadoop-common/CHANGES.txt
*
/hadoop/common/trunk/hadoop-common-project/hadoop-common/src/test/java/org/apache/hadoop/crypto/key/TestKeyShell.java
> 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)
