Re: Long running time for recently added tests in standalone-metastore

2018-01-30 Thread Vihang Karajgaonkar
+1 I think thats a great idea. Hopefully, this will help reducing some load on HiveQA jobs as well. Currently, most of the patches go through multi-iteration HiveQA runs at-least some of which could have been avoided if there is a light-weight test profile which can be run locally. This would be a

Re: Long running time for recently added tests in standalone-metastore

2018-01-30 Thread Peter Vary
+1 > On Jan 30, 2018, at 1:54 AM, Owen O'Malley wrote: > > +1 > > On Mon, Jan 29, 2018 at 4:38 PM, Alexander Kolbasov > wrote: > >> Quite reasonable. >> +1 >> >> On Mon, Jan 29, 2018 at 4:19 PM, Alan Gates wrote: >> >>> With all of the added tests in standalone-metastore/…/client directory

Re: Long running time for recently added tests in standalone-metastore

2018-01-29 Thread Owen O'Malley
+1 On Mon, Jan 29, 2018 at 4:38 PM, Alexander Kolbasov wrote: > Quite reasonable. > +1 > > On Mon, Jan 29, 2018 at 4:19 PM, Alan Gates wrote: > > > With all of the added tests in standalone-metastore/…/client directory, > the > > runtime of ‘mvn test’ in standalone-metastore went from 6 minutes

Re: Long running time for recently added tests in standalone-metastore

2018-01-29 Thread Alexander Kolbasov
Quite reasonable. +1 On Mon, Jan 29, 2018 at 4:19 PM, Alan Gates wrote: > With all of the added tests in standalone-metastore/…/client directory, the > runtime of ‘mvn test’ in standalone-metastore went from 6 minutes to 26 on > my humble laptop. We do not want to get ourselves back where the r