[
https://issues.apache.org/jira/browse/HIVE-22942?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17055892#comment-17055892
]
Zoltan Chovan commented on HIVE-22942:
--------------------------------------
So far it sounds great :) What happens when a build fails for a PR? If there
are flaky tests, we would need some way to re-trigger the run. Would it be
possible to only execute the failed tests for the same commit?
If we already using k8s, do you think it would be feasible to introduce
multiple types of backend dbs for certain tests? We have a lot of directsql
around TxnHandler and HMS, that would greatly benefit from that. The backend db
could be spun up on-demand just for some tests that are flagged maybe.
> Replace PTest with an alternative
> ---------------------------------
>
> Key: HIVE-22942
> URL: https://issues.apache.org/jira/browse/HIVE-22942
> Project: Hive
> Issue Type: Improvement
> Reporter: Zoltan Haindrich
> Assignee: Zoltan Haindrich
> Priority: Major
> Labels: pull-request-available
> Time Spent: 10m
> Remaining Estimate: 0h
>
> I never opened a jira about this...but it might actually help collect ideas
> and actually start going somewhere sooner than later :D
> Right now we maintain the ptest2 project inside Hive to be able to run Hive
> tests in a distributed fashion...the backstab of this solution is that we are
> putting much effort into maintaining a distributed test execution framework...
> I think it would be better if we could find an off the shelf solution for the
> task and migrate to that instead of putting more efforts into the ptest
> framework
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
