[ 
https://issues.apache.org/jira/browse/HIVE-13511?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Siddharth Seth updated HIVE-13511:
----------------------------------
    Attachment: HIVE-13511.03.addendum.patch

Addendum patch over the previous one whcih changes the module name to 
"itests/qtest" and "itests/qtests-spark".

[~spena] - the jenkins jobs are broken at the moment because of the commit 
earlier today. I think you'll need to restart the jenkins server.
Up to you whether you want to revert this patch, or apply the addendum and try. 
Thanks, and sorry for the breaking the tests - need a better way to test out 
changes to ptest. 

Sample output is here - which shows an attempt to pushd into qtest from the top 
level - which is what the addendum patch should fix. Looking at the script more 
- I think there's plenty more time wasted by running the find commands - which 
can be looked at in a separate jira.
http://ec2-50-18-27-0.us-west-1.compute.amazonaws.com/logs/PreCommit-HIVE-MASTER-Build-408/succeeded/TestCliDriver-vector_grouping_sets.q-exchange_partition.q-udf_cbrt.q-and-12-more/TestCliDriver-vector_grouping_sets.q-exchange_partition.q-udf_cbrt.q-and-12-more.txt

> Run clidriver tests from within the qtest dir for the precommit tests
> ---------------------------------------------------------------------
>
>                 Key: HIVE-13511
>                 URL: https://issues.apache.org/jira/browse/HIVE-13511
>             Project: Hive
>          Issue Type: Sub-task
>            Reporter: Siddharth Seth
>            Assignee: Siddharth Seth
>             Fix For: 2.1.0
>
>         Attachments: HIVE-13511.01.patch, HIVE-13511.02.patch, 
> HIVE-13511.03.addendum.patch, HIVE-13511.03.patch, example_maven-test.txt, 
> example_testExecution.txt, failedScriptPostPatch.txt
>
>
> The tests are currently run from the itests directory - which means there's 
> additional overhead of having to at least check whether files have changed. 
> Will attach a sample output - this adds up to 40+ seconds per batch. Getting 
> rid of this should be a reasonable saving overall.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to