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

Hudson commented on HBASE-25476:
--------------------------------

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

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






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


(/) {color:green}+1 jdk11 hadoop3 checks{color}
-- For more information [see jdk11 
report|https://ci-hadoop.apache.org/job/HBase/job/HBase%20Nightly/job/master/184/JDK11_20Nightly_20Build_20Report_20_28Hadoop3_29/]


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


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


> Enable error prone check in pre commit
> --------------------------------------
>
>                 Key: HBASE-25476
>                 URL: https://issues.apache.org/jira/browse/HBASE-25476
>             Project: HBase
>          Issue Type: Improvement
>          Components: build
>            Reporter: Duo Zhang
>            Assignee: Duo Zhang
>            Priority: Major
>             Fix For: 3.0.0-alpha-1, 2.5.0, 2.3.5, 2.4.2
>
>
> This has been a pain in the past as the output is not stable, but in 
> HBASE-25333, we found that some checks in error prone is really useful.
> So here I think we need to find a way to try to enable it again in pre commit.
> Maybe we could only check for ERROR level problems as it will cause 
> compilation error.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Reply via email to