[
https://issues.apache.org/jira/browse/MAPREDUCE-7197?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16877775#comment-16877775
]
Adam Antal commented on MAPREDUCE-7197:
---------------------------------------
Patchset v4 addresses the not indentation related checkstyle errors, and also
added the "ignore deprecation warning" annotation for a testcase (I didn't
touch that part meaningfully, just the assertEquals statements have been
changed).
ASF license is unrelated, this is some file crated by the tests.
Also I'm unsure why hadoop-mapreduce-client-jobclient failed. Pending on
jenkins.
Feel free to review/comment on it.
> Fix order of actual and expected expression in assert statements
> ----------------------------------------------------------------
>
> Key: MAPREDUCE-7197
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-7197
> Project: Hadoop Map/Reduce
> Issue Type: Improvement
> Affects Versions: 3.2.0
> Reporter: Adam Antal
> Assignee: Adam Antal
> Priority: Major
> Attachments: MAPREDUCE-7197.001.patch, MAPREDUCE-7197.002.patch,
> MAPREDUCE-7197.003.patch, MAPREDUCE-7197.004.patch,
> old-approx-from-HADOOP-12693
>
>
> Fix order of actual and expected expression in assert statements which gives
> misleading message when test case fails. Attached file has some of the places
> where it is placed wrongly.
> {code:java}
> [ERROR]
> testNodeRemovalGracefully(org.apache.hadoop.yarn.server.resourcemanager.TestResourceTrackerService)
> Time elapsed: 3.385 s <<< FAILURE!
> java.lang.AssertionError: Shutdown nodes should be 0 now expected:<1> but
> was:<0>
> {code}
> For long term, [AssertJ|http://joel-costigliola.github.io/assertj/] can be
> used for new test cases which avoids such mistakes.
> This is a follow-up Jira on the fix for the MR project.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
