You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@hbase.apache.org by Gomathivinayagam Muthuvinayagam <sa...@gmail.com> on 2014/08/15 20:17:11 UTC
Decrypting Hadoop QA response
I got the automated message from Hadoop QA
https://issues.apache.org/jira/browse/HBASE-11699?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14098769#comment-14098769
I have few questions on this, your help would be appreciated
1) it says -1 for javadoc warnings, I dont know how to fix that
2) line lengths are longer for the proto file, when I look at eclipse,
those lines are shorter only.Is there any tool I can use it to format?
3) If the overall result is -1, even if the unit test cases are running
fine, should I take it as a failure one?
Thanks & Regards,
Re: Decrypting Hadoop QA response
Posted by Ted Yu <yu...@gmail.com>.
Fro #1, see
https://builds.apache.org/job/PreCommit-HBASE-Build/10458/artifact/patchprocess/patchJavadocWarnings.txt
for details on the javadoc warning.
For #2, the long lines seem to come from
hbase-protocol/src/main/java/org/apache/hadoop/hbase/protobuf/generated/MasterProtos.java
You don't need to worry about the long lines there.
Cheers
On Fri, Aug 15, 2014 at 11:17 AM, Gomathivinayagam Muthuvinayagam <
sankarmail@gmail.com> wrote:
> I got the automated message from Hadoop QA
>
> https://issues.apache.org/jira/browse/HBASE-11699?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14098769#comment-14098769
>
> I have few questions on this, your help would be appreciated
>
> 1) it says -1 for javadoc warnings, I dont know how to fix that
> 2) line lengths are longer for the proto file, when I look at eclipse,
> those lines are shorter only.Is there any tool I can use it to format?
> 3) If the overall result is -1, even if the unit test cases are running
> fine, should I take it as a failure one?
>
> Thanks & Regards,
>