[
https://issues.apache.org/jira/browse/HBASE-24280?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17125169#comment-17125169
]
Nick Dimiduk commented on HBASE-24280:
--------------------------------------
Oh, I see. The variable {{BRANCH_NAME}} is the name of the PR branch on GitHub.
I think you actually want {{CHANGE_TARGET}}.
>From
>https://builds.apache.org/blue/organizations/jenkins/HBase-PreCommit-GitHub-PR/detail/PR-1834/1/pipeline/
{noformat}
...
[2020-06-02T19:15:21.035Z] BRANCH_NAME=PR-1834
...
[2020-06-02T19:15:21.036Z] CHANGE_TARGET=branch-2.3
...
{noformat}
> Hadoop2 and Hadoop3 profiles being activated simultaneously causing test
> failures
> ---------------------------------------------------------------------------------
>
> Key: HBASE-24280
> URL: https://issues.apache.org/jira/browse/HBASE-24280
> Project: HBase
> Issue Type: Bug
> Reporter: Josh Elser
> Assignee: Istvan Toth
> Priority: Major
> Fix For: 2.3.0
>
> Attachments: HBASE-24280.master.001.patch,
> TEST-org.apache.hadoop.hbase.rest.TestSecureRESTServer.xml
>
>
> [~ndimiduk] pointed out that, after this change went in, TestSecureRESTServer
> started failing with Hadoop3 on branch-2.3
> https://builds.apache.org/job/HBase%20Nightly/job/branch-2.3/56/
> Of course, I ran this with 1.8.0_241 and Maven 3.6.33 and it passed :) {{mvn
> clean package -Dtest=TestSecureRESTServer -Dhadoop.profile=3.0
> -DfailIfNoTests=false}}
> FYI [~stoty] in case you can repro a failure and want to dig in. Feel free to
> re-assign.
> It looks like we didn't have a nightly run of branch-2.2 due to docker
> container build issues. Will be interesting to see if it fails there. It did
> not fail the master nightly.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
