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

stack commented on HBASE-22052:
-------------------------------

The pushed addendum2 didn't work either. Nightly hung 9 hours and was killed. 
Trying to run the failing IT test locally because log file is not available on 
build box... trying to repro this:

21:54:03  + 
/home/jenkins/jenkins-slave/workspace/HBase_Nightly_branch-2.1-S5GA5UYEBNAEMXMEVWGCXQO7HNXNX47M5KZBXWNNXMFDW4LAP27Q/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.7.1-tests.jar 
hadoop-2/share/hadoop/mapreduce/hadoop-mapreduce-client-jobclient-2.7.1-tests.jar

> pom cleaning; filter out jersey-core in hadoop2 to match hadoop3 and remove 
> redunant version specifications
> -----------------------------------------------------------------------------------------------------------
>
>                 Key: HBASE-22052
>                 URL: https://issues.apache.org/jira/browse/HBASE-22052
>             Project: HBase
>          Issue Type: Task
>            Reporter: stack
>            Assignee: stack
>            Priority: Major
>             Fix For: 2.2.0, 2.0.5, 2.1.4
>
>         Attachments: HBASE-22052-branch-2.1.003.addendum2.txt, 
> HBASE-22052.2.1.003.addendum1.txt, HBASE-22052.branch-2.0.001.patch, 
> HBASE-22052.branch-2.0.002.patch, HBASE-22052.branch-2.0.002.patch, 
> HBASE-22052.branch-2.0.003.patch, HBASE-22052.branch-2.0.004.patch, 
> HBASE-22052.branch-2.1.001.patch, HBASE-22052.branch-2.1.002.patch, 
> HBASE-22052.branch-2.1.003.patch, HBASE-22052.branch-2.2.001.patch, 
> HBASE-22052.branch-2.2.002.patch
>
>
> Working on HBASE-22029, where we fail compile of hbase-it module four hours 
> into an RC build, it looks like transitive include of jersey-core is the 
> culprit. hadoop3 profile does a bunch of jersey-core exclusions. This issue 
> is about having hadoop2 profile and hadoop3 profiles match around jersey-core 
> treatment. Some miscellaneous cleanups are also done.



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

Reply via email to