hadoop-mapreduce-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Dick King (JIRA)" <j...@apache.org>
Subject [jira] Created: (MAPREDUCE-770) org.apache.hadoop.tools.TestCopyFiles may leave junk files when an assertion fails
Date Fri, 17 Jul 2009 21:43:14 GMT
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
            Reporter: Dick King


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.


Mime
View raw message