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

Hudson commented on HBASE-21895:
--------------------------------

Results for branch master
        [build #881 on 
builds.a.o|https://builds.apache.org/job/HBase%20Nightly/job/master/881/]: (x) 
*{color:red}-1 overall{color}*
----
details (if available):

(/) {color:green}+1 general checks{color}
-- For more information [see general 
report|https://builds.apache.org/job/HBase%20Nightly/job/master/881//General_Nightly_Build_Report/]




(x) {color:red}-1 jdk8 hadoop2 checks{color}
-- For more information [see jdk8 (hadoop2) 
report|https://builds.apache.org/job/HBase%20Nightly/job/master/881//JDK8_Nightly_Build_Report_(Hadoop2)/]


(/) {color:green}+1 jdk8 hadoop3 checks{color}
-- For more information [see jdk8 (hadoop3) 
report|https://builds.apache.org/job/HBase%20Nightly/job/master/881//JDK8_Nightly_Build_Report_(Hadoop3)/]


(/) {color:green}+1 source release artifact{color}
-- See build output for details.


(/) {color:green}+1 client integration test{color}


> Error prone upgrade
> -------------------
>
>                 Key: HBASE-21895
>                 URL: https://issues.apache.org/jira/browse/HBASE-21895
>             Project: HBase
>          Issue Type: Task
>          Components: build
>            Reporter: Duo Zhang
>            Assignee: Kevin Risden
>            Priority: Major
>             Fix For: 3.0.0
>
>         Attachments: HBASE-21895-v4.patch, HBASE-21895-v5.patch, 
> HBASE-21895-v6.patch, HBASE-21895.master.001.patch, 
> HBASE-21895.master.002.patch, HBASE-21895.master.003.patch
>
>
> As shown in HBASE-21890 , the error prone warnings are truly useful.
> But now, the javac warnings section in the pre commit result is messed up, it 
> always reports unrelated warnings. Need to take a look at it.
> And also, we should try out best to clean up the warnings.



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

Reply via email to