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

Hadoop QA commented on HADOOP-14782:
------------------------------------

| (x) *{color:red}-1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
| {color:blue}0{color} | {color:blue} reexec {color} | {color:blue}  0m  
0s{color} | {color:blue} Docker mode activated. {color} |
| {color:blue}0{color} | {color:blue} patch {color} | {color:blue}  0m  
3s{color} | {color:blue} The patch file was not named according to hadoop's 
naming conventions. Please see https://wiki.apache.org/hadoop/HowToContribute 
for instructions. {color} |
| {color:red}-1{color} | {color:red} patch {color} | {color:red}  0m  5s{color} 
| {color:red} HADOOP-14782 does not apply to trunk. Rebase required? Wrong 
Branch? See https://wiki.apache.org/hadoop/HowToContribute for help. {color} |
\\
\\
|| Subsystem || Report/Notes ||
| JIRA Issue | HADOOP-14782 |
| JIRA Patch URL | 
https://issues.apache.org/jira/secure/attachment/12882254/add-sw_64.diff |
| Console output | 
https://builds.apache.org/job/PreCommit-HADOOP-Build/13054/console |
| Powered by | Apache Yetus 0.6.0-SNAPSHOT   http://yetus.apache.org |


This message was automatically generated.



> Added sw_64 CPU architecture
> ----------------------------
>
>                 Key: HADOOP-14782
>                 URL: https://issues.apache.org/jira/browse/HADOOP-14782
>             Project: Hadoop Common
>          Issue Type: Improvement
>    Affects Versions: 2.7.3
>         Environment: OS is Raise release 2.0.5 (Beta) using RPM package 
> manager
> CPU is SW1610
>            Reporter: Xing
>              Labels: patch
>             Fix For: 2.7.3
>
>         Attachments: add-sw_64.diff
>
>




--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to