Thanks Jim for this information.
I'd a few more queries - What is the system configuration you are using on which the estimates you gave hold true? RAM, HDD, CPU or any other requirement? We also wanted to know pre-requisites to run each of these tests so that we start preparing for it upfront. For e.g. backend tests does not need any test data, however frontend tests do need test data to be generated and loaded. Are there any detailed documents listing steps to prepare and execute all these tests. Test data generation is being done by default using buildall.sh with -testdata argument. Can we customize this step to generate different data or some scaled (small scale) data? Do we even need to do so to ensure Impala works with different data sets? Also, does time for each of these tests as you mentioned take test data generation and loading time into consideration or is it purely test execution duration? We also observed test data loading takes more than 5 hrs at our end both on x86 and power? How much time does it take for you? Also, when should we really need to generate test data from scratch (-format argument to buildall.sh)? I hope it is not needed every time. Should we consider testing of release build and debug build separately? Do you expect any differences in behavior? Also, what all dependencies will need to be rebuilt in release mode? We are also open for a call if any developer/tester is interested in discussing these points. Actually, we need this test plan a bit urgent as couple of our customers are waiting for timeline. Thanks, Nishidha ----- Forwarded by Nishidha Panpaliya/Austin/Contr/IBM on 05/13/2016 11:11 AM ----- From: Sudarshan Jagadale/Austin/Contr/IBM To: Nishidha Panpaliya/Austin/Contr/IBM@IBMUS Date: 05/13/2016 10:54 AM Subject: Fw: Impala tests and estimate FYI Thanks and Regards Sudarshan Jagadale Power Open Source Solutions ----- Forwarded by Sudarshan Jagadale/Austin/Contr/IBM on 05/13/2016 10:53 AM ----- From: Jim Apple <[email protected]> To: [email protected] Cc: Manish Patil/Austin/Contr/IBM@IBMUS, Sudarshan Jagadale/Austin/Contr/IBM@IBMUS, Anup Halarnkar/Austin/Contr/IBM@IBMUS, Valencia Serrao/Austin/Contr/IBM@IBMUS Date: 05/12/2016 11:56 PM Subject: Re: Fw: Impala tests and estimate The backend tests take 12 minutes. The frontend tests take 10 seconds. The JDBC tests take 2 minutes. The custom cluster tests take 35 minutes. The end-to-end tests take 3 hours. That's in "core" mode. "exhaustive" mode quadruples the total time, IIRC, and I'd guess that's all in the end-to-end tests, but I'm not sure. On Thu, May 12, 2016 at 5:40 AM, Nishidha Panpaliya <[email protected]> wrote: Hi All, Could you please let me know the scope of Impala unit testing? I mean what all tests should be executed and ensured. I saw BE, FE, EE, JDBC, Cluster tests in run-all-tests.sh. And a guess estimate of how much time each of these take to execute? Thanks, Nishidha ----- Forwarded by Nishidha Panpaliya/Austin/Contr/IBM on 05/12/2016 06:07 PM ----- From: Nishidha Panpaliya/Austin/Contr/IBM To: [email protected] Cc: "Jim Apple" <[email protected]>, Manish Patil/Austin/Contr/IBM@IBMUS, Sudarshan Jagadale/Austin/Contr/IBM@IBMUS, "Tim Armstrong" <[email protected]>, Valencia Serrao/Austin/Contr/IBM@IBMUS Date: 03/29/2016 06:59 PM Subject: Re: Impala tests and estimate Just one more request. We'll be thankful if we could also get to know the count of each of these tests (for e.g. there are 71 backend tests). Thanks, Nishidha Nishidha Panpaliya---03/29/2016 10:05:29 AM---Hi All, I again need your help in understanding Impala tests to be run and ensured and their estimat From: Nishidha Panpaliya/Austin/Contr/IBM To: [email protected], "Tim Armstrong" < [email protected]>, "Jim Apple" <[email protected]> Cc: Sudarshan Jagadale/Austin/Contr/IBM@IBMUS, Manish Patil/Austin/Contr/IBM@IBMUS, Valencia Serrao/Austin/Contr/IBM@IBMUS Date: 03/29/2016 10:05 AM Subject: Impala tests and estimate Hi All, I again need your help in understanding Impala tests to be run and ensured and their estimates. Last time, I know you had given way to run only backend tests and it was helpful to us. I've also gone through run-all-tests.sh which triggers backend test, frontend test, end-to-end tests, etc. Could you provide me individual commands to run each of them and if any setup steps are required? Also, I would like to know if there are any specific system requirements that I must have up-front to run all these tests. Along with these commands/scripts, I'm also interested in knowing how much time each of these tests take to run, if we do not run into any issues. This is required to know the guess estimate of how long will this activity be taking from now. Thanks in advance, Nishidha
