You are viewing a plain text version of this content. The canonical link for it is here.
Posted to mapreduce-issues@hadoop.apache.org by "Dick King (JIRA)" <ji...@apache.org> on 2009/07/18 00:36:15 UTC

[jira] Commented: (MAPREDUCE-770) org.apache.hadoop.tools.TestCopyFiles may leave junk files when an assertion fails

    [ https://issues.apache.org/jira/browse/MAPREDUCE-770?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12732764#action_12732764 ] 

Dick King commented on MAPREDUCE-770:
-------------------------------------

ant clean does not solve the problem.  Some of the junk files are left on HDFS .

> org.apache.hadoop.tools.TestCopyFiles may leave junk files when an assertion fails
> ----------------------------------------------------------------------------------
>
>                 Key: MAPREDUCE-770
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-770
>             Project: Hadoop Map/Reduce
>          Issue Type: Bug
>          Components: test
>            Reporter: Dick King
>            Priority: Minor
>
> In most of the testXxxYyyZzz methods, the code runs:
>    preliminaries
>    ToolRunner( ..., new String[] { local and DFS filenames and more filenames });
>    assertMaybe("this result stank", conditions);
>    assertMaybe("this other result stank", conditions);
>    deldir(deletee's name);
>    deldir(second deletee's name);
> The assertMaybe's throw AssertionFailedError .  That's what they DO.  Shouldn't this stuff be protected with a try ... finally construct?

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.