[
https://issues.apache.org/jira/browse/PHOENIX-6105?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17185388#comment-17185388
]
Istvan Toth commented on PHOENIX-6105:
--------------------------------------
True.
Until we get some shiny new Jenkins nodes, we'll have compromise somewhere.
We could run on 2.3, but then we'd have to disable the SplitSystemCatalog
tests, or find some way to split the tables that don't trigger the HBase bug
(or fix HBase, but even that wouldn't be an immediate solution, unless we test
with snapshots )
I can clone the precommit job to run with 2.3, and you could trigger it
manually for 2.3 specific patches. Would that help ?
> Run precommit tests with HBase 2.2 on master
> --------------------------------------------
>
> Key: PHOENIX-6105
> URL: https://issues.apache.org/jira/browse/PHOENIX-6105
> Project: Phoenix
> Issue Type: Task
> Reporter: Istvan Toth
> Assignee: Istvan Toth
> Priority: Major
>
> Since we have flakey tests that only fail with HBase 2.1, and HBase 2.3
> (different sets), set up the Precommit test job to run with HBase 2.2, as
> that minimizes the number of false positive test failures on the precommit
> job.
> The afromentioned flakey tests are probably the results of HBase bugs, though
> this warrants further investigation.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
