You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Nick Dimiduk (Jira)" <ji...@apache.org> on 2020/05/13 18:09:00 UTC
[jira] [Commented] (HBASE-24347) Hadoop2&Hadoop3 profiles are both
active when pre-commit PR builds run
[ https://issues.apache.org/jira/browse/HBASE-24347?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17106540#comment-17106540 ]
Nick Dimiduk commented on HBASE-24347:
--------------------------------------
[~stoty] [~elserj] are you guys tracking on this item as well?
Maybe [~busbey] can comment as to the reason why PRs do not use master's personality? I speculate that it's because we want PRs to be able to test personality changes.
> Hadoop2&Hadoop3 profiles are both active when pre-commit PR builds run
> ----------------------------------------------------------------------
>
> Key: HBASE-24347
> URL: https://issues.apache.org/jira/browse/HBASE-24347
> Project: HBase
> Issue Type: Sub-task
> Components: build
> Reporter: Michael Stack
> Priority: Major
>
> We need the magic done in the parent out in our precommit builds too. See how https://github.com/apache/hbase/pull/1664 fails in hbase-rest w/ complaint about jersey; this is a symptom of double hadoop2+hadoop3 profile activation.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)