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

Hudson commented on HBASE-27599:
--------------------------------

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

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




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


(x) {color:red}-1 jdk11 hadoop3 checks{color}
-- For more information [see jdk11 
report|https://ci-hbase.apache.org/job/HBase%20Nightly/job/master/769/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}


> Cleanup wrong dependency in dependencyManagement
> ------------------------------------------------
>
>                 Key: HBASE-27599
>                 URL: https://issues.apache.org/jira/browse/HBASE-27599
>             Project: HBase
>          Issue Type: Bug
>          Components: build, dependencies, hadoop3, pom
>            Reporter: tianhang tang
>            Assignee: tianhang tang
>            Priority: Major
>             Fix For: 3.0.0-alpha-4
>
>         Attachments: screenshot-1.png, screenshot-2.png
>
>
> In HBASE-27340 added a hadoop-3.0 profile in hbase-shaded-testing-util pom, 
> but missed the version of hadoop-common test jar: 
> [HBASE-27340|https://github.com/apache/hbase/commit/1b5403cf7d906a22c20bd4f025566a2a5f895d44]
>  !screenshot-2.png! 
> This will cause build failure:
>  !screenshot-1.png! 
> But I still don't know why this problem does not necessarily arise...



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to