hadoop-mapreduce-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Eric Badger (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (MAPREDUCE-6580) Test failure : TestMRJobsWithProfiler
Date Mon, 21 Mar 2016 20:55:25 GMT

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

Eric Badger commented on MAPREDUCE-6580:

I am able to get TestMRJobsWithProfiler#testDifferentProfilers to fail consistently on my
Mac. However, I am not able to get it to fail on my Linux box or on either box when running
testDefaultProfiler. On my mac, I have found that the problem is with the hprof option "times"
in TestMRJobsWithProfiler.java:137 (-agentlib:hprof=cpu=times,heap=sites,force=n,thread=y,verbose=n,"
+ "file=%s). This is causing the JVM to screw up and fail seemingly before it even begins
to start the container. 

Additionally, the "times" option is incredibly expensive and slows the JVM down a ton, making
the test very likely to timeout on a busy Jenkins instance given the 150 second test timeout.
IMO using "samples" instead of "times" would be much better. Using samples, the test passes
on my mac and speeds the test up by almost 2x (74.8s vs. 145.5s on my Linux machine). Using
"samples" would get rid of the hprof error on my mac and also speed up the test considerably,
reducing the chance of test timeouts.

Is there any reason that we can't use "samples" instead of "times" for the profiler? 

> Test failure : TestMRJobsWithProfiler
> -------------------------------------
>                 Key: MAPREDUCE-6580
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-6580
>             Project: Hadoop Map/Reduce
>          Issue Type: Bug
>            Reporter: Rohith Sharma K S
> From [https://builds.apache.org/job/PreCommit-YARN-Build/9976/artifact/patchprocess/patch-unit-hadoop-mapreduce-project_hadoop-mapreduce-client_hadoop-mapreduce-client-jobclient-jdk1.8.0_66.txt]
TestMRJobsWithProfiler fails intermittently
> {code}
> Running org.apache.hadoop.mapreduce.v2.TestMRJobsWithProfiler
> Tests run: 2, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 212.973 sec <<<
FAILURE! - in org.apache.hadoop.mapreduce.v2.TestMRJobsWithProfiler
> testDifferentProfilers(org.apache.hadoop.mapreduce.v2.TestMRJobsWithProfiler)  Time elapsed:
133.116 sec  <<< FAILURE!
> java.lang.AssertionError: expected:<4> but was:<1>
> 	at org.junit.Assert.fail(Assert.java:88)
> 	at org.junit.Assert.failNotEquals(Assert.java:743)
> 	at org.junit.Assert.assertEquals(Assert.java:118)
> 	at org.junit.Assert.assertEquals(Assert.java:555)
> 	at org.junit.Assert.assertEquals(Assert.java:542)
> 	at org.apache.hadoop.mapreduce.v2.TestMRJobsWithProfiler.testProfilerInternal(TestMRJobsWithProfiler.java:212)
> 	at org.apache.hadoop.mapreduce.v2.TestMRJobsWithProfiler.testDifferentProfilers(TestMRJobsWithProfiler.java:117)
> {code}

This message was sent by Atlassian JIRA

View raw message