[jira] [Commented] (HBASE-22471) Our nightly jobs for master and branch-2 are still using hadoop-2.7.1 in integration test

2019-05-29 Thread Hudson (JIRA)


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

Hudson commented on HBASE-22471:


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


[jira] [Commented] (HBASE-22471) Our nightly jobs for master and branch-2 are still using hadoop-2.7.1 in integration test

2019-05-29 Thread Hudson (JIRA)


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

Hudson commented on HBASE-22471:


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


[jira] [Commented] (HBASE-22471) Our nightly jobs for master and branch-2 are still using hadoop-2.7.1 in integration test

2019-05-29 Thread Hudson (JIRA)


[ 
https://issues.apache.org/jira/browse/HBASE-22471?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=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)


[jira] [Commented] (HBASE-22471) Our nightly jobs for master and branch-2 are still using hadoop-2.7.1 in integration test

2019-05-29 Thread Guanghao Zhang (JIRA)


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

Guanghao Zhang commented on HBASE-22471:


{quote}[~zghaobac] Seems we still need to hold on releasing 2.2.0...
{quote}
:(

> 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)


[jira] [Commented] (HBASE-22471) Our nightly jobs for master and branch-2 are still using hadoop-2.7.1 in integration test

2019-05-28 Thread Duo Zhang (JIRA)


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

Duo Zhang commented on HBASE-22471:
---

[~zghaobac] Seems we still need to hold on releasing 2.2.0...

> 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.3.0, 2.2.1
>
> 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)


[jira] [Commented] (HBASE-22471) Our nightly jobs for master and branch-2 are still using hadoop-2.7.1 in integration test

2019-05-28 Thread Duo Zhang (JIRA)


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

Duo Zhang commented on HBASE-22471:
---

Let me commit this first and then open new issue to address the hadoop 3 
problem.

> 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.3.0, 2.2.1
>
> 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)


[jira] [Commented] (HBASE-22471) Our nightly jobs for master and branch-2 are still using hadoop-2.7.1 in integration test

2019-05-28 Thread Duo Zhang (JIRA)


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

Duo Zhang commented on HBASE-22471:
---

OK, now we fail with hadoop3...

> 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.3.0, 2.2.1
>
> 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)


[jira] [Commented] (HBASE-22471) Our nightly jobs for master and branch-2 are still using hadoop-2.7.1 in integration test

2019-05-28 Thread Hudson (JIRA)


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

Hudson commented on HBASE-22471:


Results for branch master
[build #1050 on 
builds.a.o|https://builds.apache.org/job/HBase%20Nightly/job/master/1050/]: (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/1050//General_Nightly_Build_Report/]




(/) {color:green}+1 jdk8 hadoop2 checks{color}
-- For more information [see jdk8 (hadoop2) 
report|https://builds.apache.org/job/HBase%20Nightly/job/master/1050//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/master/1050//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/master/1050//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.3.0, 2.2.1
>
> 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)


[jira] [Commented] (HBASE-22471) Our nightly jobs for master and branch-2 are still using hadoop-2.7.1 in integration test

2019-05-28 Thread Sean Busbey (JIRA)


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

Sean Busbey commented on HBASE-22471:
-

belated +1, that's a nice way to do it.

clearing the workspace manually involves digging through pipeline stages to 
find the node assignment, which will get you a link to the workspace, which 
will have a link to clear it. It's a big pain. This is much better.

> 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.3.0, 2.2.1
>
> 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)


[jira] [Commented] (HBASE-22471) Our nightly jobs for master and branch-2 are still using hadoop-2.7.1 in integration test

2019-05-28 Thread Duo Zhang (JIRA)


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

Duo Zhang commented on HBASE-22471:
---

Seems worked

https://builds.apache.org/job/HBase%20Nightly/job/master/1048/console

{noformat}
Delete stale hadoop 2 cache 
/home/jenkins/jenkins-slave/workspace/HBase_Nightly_master/hadoop-2.7.1-bin.tar.gz
Delete stale hadoop 3 cache 
/home/jenkins/jenkins-slave/workspace/HBase_Nightly_master/hadoop-3.0.0-bin.tar.gz

15:21:44  ++ ls -1 
/home/jenkins/jenkins-slave/workspace/HBase_Nightly_master/hadoop-2.8.2-bin.tar.gz
15:21:44  ++ head -n 1
15:21:44  + 
artifact=/home/jenkins/jenkins-slave/workspace/HBase_Nightly_master/hadoop-2.8.2-bin.tar.gz
15:21:44  + tar --strip-components=1 -xzf 
/home/jenkins/jenkins-slave/workspace/HBase_Nightly_master/hadoop-2.8.2-bin.tar.gz
 -C hadoop-2
15:21:48  + 
/home/jenkins/jenkins-slave/workspace/HBase_Nightly_master/component/dev-support/hbase_nightly_pseudo-distributed-test.sh
 --single-process --working-dir output-integration/hadoop-2 
--hbase-client-install hbase-client hbase-install hadoop-2/bin/hadoop 
hadoop-2/share/hadoop/yarn/test/hadoop-yarn-server-tests-2.8.2-tests.jar 
hadoop-2/share/hadoop/mapreduce/hadoop-mapreduce-client-jobclient-2.8.2-tests.jar
{noformat}

> 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.3.0, 2.2.1
>
> 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)


[jira] [Commented] (HBASE-22471) Our nightly jobs for master and branch-2 are still using hadoop-2.7.1 in integration test

2019-05-28 Thread HBase QA (JIRA)


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

HBase QA commented on HBASE-22471:
--

| (/) *{color:green}+1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
| {color:blue}0{color} | {color:blue} reexec {color} | {color:blue}  0m 
49s{color} | {color:blue} Docker mode activated. {color} |
|| || || || {color:brown} Prechecks {color} ||
| {color:blue}0{color} | {color:blue} shelldocs {color} | {color:blue}  0m  
0s{color} | {color:blue} Shelldocs was not available. {color} |
| {color:green}+1{color} | {color:green} @author {color} | {color:green}  0m  
0s{color} | {color:green} The patch does not contain any @author tags. {color} |
|| || || || {color:brown} master Compile Tests {color} ||
|| || || || {color:brown} Patch Compile Tests {color} ||
| {color:green}+1{color} | {color:green} shellcheck {color} | {color:green}  0m 
 0s{color} | {color:green} There were no new shellcheck issues. {color} |
| {color:green}+1{color} | {color:green} whitespace {color} | {color:green}  0m 
 0s{color} | {color:green} The patch has no whitespace issues. {color} |
|| || || || {color:brown} Other Tests {color} ||
| {color:green}+1{color} | {color:green} asflicense {color} | {color:green}  0m 
10s{color} | {color:green} The patch does not generate ASF License warnings. 
{color} |
| {color:black}{color} | {color:black} {color} | {color:black}  1m 15s{color} | 
{color:black} {color} |
\\
\\
|| Subsystem || Report/Notes ||
| Docker | Client=17.05.0-ce Server=17.05.0-ce base: 
https://builds.apache.org/job/PreCommit-HBASE-Build/438/artifact/patchprocess/Dockerfile
 |
| JIRA Issue | HBASE-22471 |
| JIRA Patch URL | 
https://issues.apache.org/jira/secure/attachment/12970041/HBASE-22471.patch |
| Optional Tests |  dupname  asflicense  shellcheck  shelldocs  |
| uname | Linux 36fc14bb0dc8 4.4.0-143-generic #169~14.04.2-Ubuntu SMP Wed Feb 
13 15:00:41 UTC 2019 x86_64 GNU/Linux |
| Build tool | maven |
| Personality | dev-support/hbase-personality.sh |
| git revision | master / 97090560a5 |
| maven | version: Apache Maven 3.5.4 
(1edded0938998edf8bf061f1ceb3cfdeccf443fe; 2018-06-17T18:33:14Z) |
| shellcheck | v0.4.4 |
| Max. process+thread count | 41 (vs. ulimit of 1) |
| modules | C: . U: . |
| Console output | 
https://builds.apache.org/job/PreCommit-HBASE-Build/438/console |
| Powered by | Apache Yetus 0.9.0 http://yetus.apache.org |


This message was automatically generated.



> 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.3.0, 2.2.1
>
> 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)


[jira] [Commented] (HBASE-22471) Our nightly jobs for master and branch-2 are still using hadoop-2.7.1 in integration test

2019-05-28 Thread Duo Zhang (JIRA)


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

Duo Zhang commented on HBASE-22471:
---

Try to delete the stale hadoop cache. As there is no way to test this in pre 
commit, tend to commit the patch to master to see if it works...

> 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.3.0, 2.2.1
>
> 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)


[jira] [Commented] (HBASE-22471) Our nightly jobs for master and branch-2 are still using hadoop-2.7.1 in integration test

2019-05-27 Thread Guanghao Zhang (JIRA)


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

Guanghao Zhang commented on HBASE-22471:


This should not be a blocker for release 2.2.0? The hadoop-2 dir is created by 
the following cmd.
{code:java}
artifact=$(ls -1 "${WORKSPACE}"/hadoop-2*.tar.gz | head -n 1)
tar --strip-components=1 -xzf "${artifact}" -C "hadoop-2"
{code}
And I checked 
[https://dist.apache.org/repos/dist/dev/hbase/2.2.0RC4/hbase-2.2.0-bin.tar.gz.] 
The hadoop jar's verion in lib is 2.8.5. And I created namespace and table by 
shell and there are no problem.

> 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
>Priority: Major
> Fix For: 3.0.0, 2.2.1
>
>
> 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)


[jira] [Commented] (HBASE-22471) Our nightly jobs for master and branch-2 are still using hadoop-2.7.1 in integration test

2019-05-25 Thread Duo Zhang (JIRA)


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

Duo Zhang commented on HBASE-22471:
---

[~busbey] Haven't find the way to clean the workspace for our nightly jobs...

> 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
>Priority: Major
>
> 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)