I'd suggest we do a rolling pre-commit test runs among the testing variables: hadoop1, hadoop2, vectorization on/off, tez, spark, etc. This way, we still have coverage on all areas with a slight bigger latency of issue discovery. Nevertheless, I think it's better to a fixed selection of the variables.
--Xuefu On Fri, Jul 11, 2014 at 1:44 PM, Eugene Koifman <ekoif...@hortonworks.com> wrote: > Can we randomly choose some subset of the tests (25% of total, for example) > to run for each cell in the test matrix? > > > On Sun, Jun 22, 2014 at 9:53 AM, Brock Noland <br...@cloudera.com> wrote: > > > Hi, > > > > I know there is an effort to enable Vectorization (HIVE-5538) by > default. I > > think we probably still want to test with it off as well. Thus our test > > matrix is exploding: > > > > MR w/o Vectorization > > MR w Vectorization > > Tez w/o Vectorization (?) > > Tez w Vectorization > > > > My concern is that whatever is enabled by default will be tested and the > > other code paths will rot. I am open to suggestions as to how to solve > this > > problem. > > > > Brock > > > > > > -- > > Thanks, > Eugene > > -- > CONFIDENTIALITY NOTICE > NOTICE: This message is intended for the use of the individual or entity to > which it is addressed and may contain information that is confidential, > privileged and exempt from disclosure under applicable law. If the reader > of this message is not the intended recipient, you are hereby notified that > any printing, copying, dissemination, distribution, disclosure or > forwarding of this communication is strictly prohibited. If you have > received this communication in error, please contact the sender immediately > and delete it from your system. Thank You. >
