hadoop-mapreduce-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jason Lowe (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (MAPREDUCE-5598) TestUserDefinedCounters.testMapReduceJob is flakey
Date Tue, 29 Oct 2013 14:06:31 GMT

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

Jason Lowe commented on MAPREDUCE-5598:

+1, lgtm.  The test build failures are unrelated, and the test passes locally for me.

There's obviously some runaway processes on the build machines from prior test runs, probably
from things like TestUberAM timing out and leaking MRAppMaster processes with tons of launcher
threads.  However I don't have access to said machines to verify that theory and clean them

I'll commit this shortly.

> 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
>         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

View raw message