[ https://issues.apache.org/jira/browse/MAPREDUCE-770?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12732771#action_12732771 ]
Dick King commented on MAPREDUCE-770: ------------------------------------- https://issues.apache.org/jira/browse/MAPREDUCE-770?focusedCommentId=12732768&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#action_12732768 could well be correct. I don't claim to have enough knowledge to refute that claim, and it's plausible. > 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.