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

Hudson commented on HBASE-15151:
--------------------------------

Results for branch branch-2
        [build #461 on 
builds.a.o|https://builds.apache.org/job/HBase%20Nightly/job/branch-2/461/]: 
(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/branch-2/461//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/branch-2/461//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/branch-2/461//JDK8_Nightly_Build_Report_(Hadoop3)/]


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


> Rely on nightly tests for findbugs compliance on existing branch
> ----------------------------------------------------------------
>
>                 Key: HBASE-15151
>                 URL: https://issues.apache.org/jira/browse/HBASE-15151
>             Project: HBase
>          Issue Type: Task
>          Components: build, test
>            Reporter: Sean Busbey
>            Assignee: Sean Busbey
>            Priority: Critical
>             Fix For: 2.0.0, 3.0.0, 2.1.0, 1.5.0, 1.3.3, 1.2.8, 1.4.3
>
>         Attachments: HBASE-15151.0.patch, HBASE-15151.1.patch
>
>
> the "-1" for extant findbugs warnings has confused interpretation of our 
> precommit checks enough that we should switch to non-strict mode.
> It will still record the number of findbugs warnings present before the 
> patch, but it'll vote "0" rather than calling attention to things via a -1.



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

Reply via email to