[
https://issues.apache.org/jira/browse/HIVE-7254?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14103541#comment-14103541
]
Szehon Ho commented on HIVE-7254:
---------------------------------
I think I see what needs to be done, its on the build machine's configuration
(not checked in) and needs to add back the other set of tez tests that Brock
accidentally removed. As I'm afraid of hosing the builds tonight, Brock or I
can do it tomorrow morning :)
Hey Brock, one idea, do you think its a good idea to add the build machine's
properties to source control? That way there is a history in case they get
changed, and all devs can easily see/modify without having to login to build
machine. Just a late night thought.
> Enhance Ptest framework config to auto-pick up list of MiniXXXDriver's test
> ---------------------------------------------------------------------------
>
> Key: HIVE-7254
> URL: https://issues.apache.org/jira/browse/HIVE-7254
> Project: Hive
> Issue Type: Test
> Components: Testing Infrastructure
> Reporter: Szehon Ho
> Assignee: Szehon Ho
> Attachments: trunk-mr2.properties
>
>
> Today, the Hive PTest infrastructure has a test-driver configuration called
> "directory", so it will run all the qfiles under that directory for that
> driver. For example, CLIDriver is configured with directory
> "ql/src/test/queries/clientpositive"
> However the configuration for the miniXXXDrivers (miniMRDriver,
> miniMRDriverNegative, miniTezDriver) run only a select number of tests under
> "directory". So we have to use the "include" configuration to hard-code a
> list of tests for it to run. This is duplicating the list of each
> miniDriver's tests already in the /itests/qtest pom file, and can get out of
> date.
> It would be nice if both got their information the same way.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
