[ 
https://issues.apache.org/jira/browse/HADOOP-10843?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14095833#comment-14095833
 ] 

Hadoop QA commented on HADOOP-10843:
------------------------------------

{color:green}+1 overall{color}.  Here are the results of testing the latest 
attachment 
  http://issues.apache.org/jira/secure/attachment/12661350/HADOOP-10843.3.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 1 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 2.0.3) warnings.

    {color:green}+1 release audit{color}.  The applied patch does not increase 
the total number of release audit warnings.

    {color:green}+1 core tests{color}.  The patch passed unit tests in 
hadoop-tools/hadoop-gridmix.

    {color:green}+1 contrib tests{color}.  The patch passed contrib unit tests.

Test results: 
https://builds.apache.org/job/PreCommit-HADOOP-Build/4466//testReport/
Console output: 
https://builds.apache.org/job/PreCommit-HADOOP-Build/4466//console

This message is automatically generated.

> TestGridmixRecord unit tests failure on PowerPC
> -----------------------------------------------
>
>                 Key: HADOOP-10843
>                 URL: https://issues.apache.org/jira/browse/HADOOP-10843
>             Project: Hadoop Common
>          Issue Type: Bug
>          Components: test, tools
>    Affects Versions: 2.2.0, 2.3.0, 2.4.0, 2.4.1
>            Reporter: Jinghui Wang
>            Assignee: Jinghui Wang
>         Attachments: HADOOP-10843.1.patch, HADOOP-10843.2.patch, 
> HADOOP-10843.3.patch
>
>
> In TestGridmixRecord#binSortTest, the test expects the comparison result of 
> WritableComparator.compareBytes, which uses UnsafeComparer, to be the integer 
> difference rather than the documented "@return 0 if equal, < 0 if left is 
> less than right, etc.". 
> TestGridmixRecord#binSortTest code snippet
> {code}
>       final int chk = WritableComparator.compareBytes(
>           out1.getData(), 0, out1.getLength(),
>           out2.getData(), 0, out2.getLength());
>       assertEquals(chk, x.compareTo(y));
>       assertEquals(chk, cmp.compare(
>             out1.getData(), 0, out1.getLength(),
>             out2.getData(), 0, out2.getLength()));
> {code}
> The code snippet below shows the Unsafe comparator behavior for 
> non-little-endian machines. 
> {code}
>       if (!littleEndian) {
>         return lessThanUnsigned(lw, rw) ? -1 : 1;
>       }
> {code}



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Reply via email to