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

Hadoop QA commented on HBASE-21990:
-----------------------------------

| (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:red}-1{color} | {color:red} patch {color} | {color:red}  0m  6s{color} 
| {color:red} HBASE-21990 does not apply to branch-2.0. Rebase required? Wrong 
Branch? See https://yetus.apache.org/documentation/0.8.0/precommit-patchnames 
for help. {color} |
\\
\\
|| Subsystem || Report/Notes ||
| JIRA Issue | HBASE-21990 |
| JIRA Patch URL | 
https://issues.apache.org/jira/secure/attachment/12961050/HBASE-21990.branch-2.0.001.patch
 |
| Console output | 
https://builds.apache.org/job/PreCommit-HBASE-Build/16231/console |
| Powered by | Apache Yetus 0.8.0   http://yetus.apache.org |


This message was automatically generated.



> puppycrawl checkstyle dtds 404... moved to sourceforge
> ------------------------------------------------------
>
>                 Key: HBASE-21990
>                 URL: https://issues.apache.org/jira/browse/HBASE-21990
>             Project: HBase
>          Issue Type: Bug
>          Components: build
>            Reporter: stack
>            Assignee: stack
>            Priority: Major
>             Fix For: 3.0.0, 2.2.0, 2.0.5, 2.1.4, 1.5.1, 1.2.12
>
>         Attachments: HBASE-21990.branch-2.0.001.patch
>
>
> Yetus flagging two  badly formatted xml files. Seemingly related are the two 
> filenotfoundexceptions that show in the xml.txt build product. 
> https://builds.apache.org/view/H-L/view/HBase/job/HBase%20Nightly/job/branch-2.0/1399/artifact/output-general/xml.txt
> The complaint is that the xml dtds are not found.
> Indeed they were moved long time ago: 
> https://github.com/checkstyle/checkstyle/issues/1571
> They were supposed to stick around at their old location but that seems to 
> have changed recently.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to