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

Hudson commented on MAPREDUCE-5598:
-----------------------------------

FAILURE: Integrated in Hadoop-Mapreduce-trunk #1594 (See 
[https://builds.apache.org/job/Hadoop-Mapreduce-trunk/1594/])
MAPREDUCE-5598. TestUserDefinedCounters.testMapReduceJob is flakey. Contributed 
by Robert Kanter (jlowe: 
http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1536724)
* /hadoop/common/trunk/hadoop-mapreduce-project/CHANGES.txt
* 
/hadoop/common/trunk/hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-jobclient/src/test/java/org/apache/hadoop/mapred/TestUserDefinedCounters.java


> TestUserDefinedCounters.testMapReduceJob is flakey
> --------------------------------------------------
>
>                 Key: MAPREDUCE-5598
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-5598
>             Project: Hadoop Map/Reduce
>          Issue Type: Bug
>          Components: test
>    Affects Versions: trunk, 2.2.0
>            Reporter: Robert Kanter
>            Assignee: Robert Kanter
>             Fix For: 3.0.0, 2.3.0, 2.2.1
>
>         Attachments: MAPREDUCE-5598.patch, MAPREDUCE-5598.patch
>
>
> {{TestUserDefinedCounters.testMapReduceJob}} is flakey.  
> We sometimes see it fail:
> {noformat}
> junit.framework.AssertionFailedError
>       at junit.framework.Assert.fail(Assert.java:48)
>       at junit.framework.Assert.assertTrue(Assert.java:20)
>       at junit.framework.Assert.assertTrue(Assert.java:27)
>       at 
> org.apache.hadoop.mapred.TestUserDefinedCounters.testMapReduceJob(TestUserDefinedCounters.java:113)
> {noformat}
> Upon investigation, the problem is that the input for the MR job in this test 
> is at {{System.getProperty("test.build.data", "/tmp") + "/input"}}.  If an 
> earlier test wrote some files there, this test will use them as part of its 
> input.  This can cause all sorts of problems with this test because its not 
> expecting the additional input data.



--
This message was sent by Atlassian JIRA
(v6.1#6144)

Reply via email to