You are viewing a plain text version of this content. The canonical link for it is here.
Posted to mapreduce-issues@hadoop.apache.org by "Andrew Wang (JIRA)" <ji...@apache.org> on 2016/03/03 02:01:23 UTC
[jira] [Commented] (MAPREDUCE-6223)
TestJobConf#testNegativeValueForTaskVmem failures
[ https://issues.apache.org/jira/browse/MAPREDUCE-6223?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15176873#comment-15176873 ]
Andrew Wang commented on MAPREDUCE-6223:
----------------------------------------
Same question here as I just posed on MAPREDUCE-6234, do we need to mark this change as incompatible if it's only present with MAPREDUCE-5785, which is already marked incompatible and only in 3.0.0?
> TestJobConf#testNegativeValueForTaskVmem failures
> -------------------------------------------------
>
> Key: MAPREDUCE-6223
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-6223
> Project: Hadoop Map/Reduce
> Issue Type: Bug
> Components: test
> Affects Versions: 3.0.0
> Reporter: Gera Shegalov
> Assignee: Varun Saxena
> Fix For: 3.0.0
>
> Attachments: MAPREDUCE-6223.001.patch, MAPREDUCE-6223.002.patch, MAPREDUCE-6223.003.patch, MAPREDUCE-6223.004.patch, MAPREDUCE-6223.005.patch, MAPREDUCE-6223.006.patch
>
>
> {code}
> Tests run: 8, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 3.328 sec <<< FAILURE! - in org.apache.hadoop.conf.TestJobConf
> testNegativeValueForTaskVmem(org.apache.hadoop.conf.TestJobConf) Time elapsed: 0.089 sec <<< FAILURE!
> java.lang.AssertionError: expected:<1024> 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.conf.TestJobConf.testNegativeValueForTaskVmem(TestJobConf.java:111)
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)