[
https://issues.apache.org/jira/browse/HADOOP-3679?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13921233#comment-13921233
]
Hadoop QA commented on HADOOP-3679:
-----------------------------------
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12632845/HADOOP-3679.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 12 new
or modified test files.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 javadoc{color}. There were no new javadoc warning messages.
{color:green}+1 eclipse:eclipse{color}. The patch built with
eclipse:eclipse.
{color:green}+1 findbugs{color}. The patch does not introduce any new
Findbugs (version 1.3.9) warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:red}-1 core tests{color}. The patch failed these unit tests in
hadoop-common-project/hadoop-common hadoop-common-project/hadoop-nfs:
org.apache.hadoop.io.file.tfile.TestTFileComparator2
{color:green}+1 contrib tests{color}. The patch passed contrib unit tests.
Test results:
https://builds.apache.org/job/PreCommit-HADOOP-Build/3629//testReport/
Console output:
https://builds.apache.org/job/PreCommit-HADOOP-Build/3629//console
This message is automatically generated.
> calls to junit Assert::assertEquals invert arguments, causing misleading
> error messages, other minor improvements.
> ------------------------------------------------------------------------------------------------------------------
>
> Key: HADOOP-3679
> URL: https://issues.apache.org/jira/browse/HADOOP-3679
> Project: Hadoop Common
> Issue Type: Test
> Components: test
> Reporter: Chris Douglas
> Priority: Minor
> Attachments: HADOOP-3679.patch
>
>
> JUnit Assert::assertEquals takes its expected and actual arguments in a
> particular order, but many unit tests invert them. The error message from a
> failed assertion can be misleading.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
