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

Hudson commented on HBASE-22471:
--------------------------------

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


(x) {color:red}-1 jdk8 hadoop3 checks{color}
-- For more information [see jdk8 (hadoop3) 
report|https://builds.apache.org/job/HBase%20Nightly/job/branch-2/1934//JDK8_Nightly_Build_Report_(Hadoop3)/]


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


(x) {color:red}-1 client integration test{color}
--Failed when running client tests on top of Hadoop 3. [see log for 
details|https://builds.apache.org/job/HBase%20Nightly/job/branch-2/1934//artifact/output-integration/hadoop-3.log].
 (note that this means we didn't check the Hadoop 3 shaded client)


> Our nightly jobs for master and branch-2 are still using hadoop-2.7.1 in 
> integration test
> -----------------------------------------------------------------------------------------
>
>                 Key: HBASE-22471
>                 URL: https://issues.apache.org/jira/browse/HBASE-22471
>             Project: HBase
>          Issue Type: Bug
>          Components: build
>            Reporter: Duo Zhang
>            Assignee: Duo Zhang
>            Priority: Major
>             Fix For: 3.0.0, 2.2.0, 2.3.0, 2.1.6
>
>         Attachments: HBASE-22471.patch
>
>
> We use ls to get the hadoop 2 jars, so maybe the problem is that the 2.7.1 
> jars are already there for a long time. We need to clean the workspace.



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

Reply via email to