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

["Allen Wittenauer (JIRA)" <ji...@apache.org>]

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

Allen Wittenauer resolved MAPREDUCE-770.
----------------------------------------

    Resolution: Fixed

Stale? I'm going to stale.

> 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 was sent by Atlassian JIRA
(v6.2#6252)