[ https://issues.apache.org/jira/browse/HBASE-24280?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17121389#comment-17121389 ]
Hudson commented on HBASE-24280: -------------------------------- Results for branch branch-2.2 [build #883 on builds.a.o|https://builds.apache.org/job/HBase%20Nightly/job/branch-2.2/883/]: (/) *{color:green}+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/883//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/branch-2.2/883//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/883//JDK8_Nightly_Build_Report_(Hadoop3)/] (/) {color:green}+1 source release artifact{color} -- See build output for details. (/) {color:green}+1 client integration test{color} > 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)