> > master-mr2.properties has to be updated on the ptest servers and restarted > afaik (atleast it used to be).
Don't think we need a restart. Just updating the properties file should be enough. I have updated the test configuration so that these tests are skipped from batching for now. I still think we should find a better way to to speed up these tests since this will potentially increase the time taken for all the jobs now. Lets see how much of time it adds to the overall time taken for each job. If its significant, can we split these tests into smaller ones so that we can still run them in parallel. I see the next job id in the queue is #14526. I will keep an eye on it to see if the configuration change has taken effect. On Wed, Oct 17, 2018 at 3:26 AM, Peter Vary <pv...@cloudera.com.invalid> wrote: > You should go to the ptest server itself and modify > /usr/local/hiveptest/profiles/master-mr2.properties to change the > configuration > > > On Oct 17, 2018, at 11:36, Prasanth Jayachandran < > pjayachand...@hortonworks.com> wrote: > > > > Hi > > > > master-mr2.properties has to be updated on the ptest servers and > restarted afaik (atleast it used to be). > > > > Thanks > > Prasanth > > > > > > > > On Wed, Oct 17, 2018 at 2:10 AM -0700, "Anishek Agarwal" < > anis...@apache.org<mailto:anis...@apache.org>> wrote: > > > > > > Hello, > > > > There are few tests w.r.t to Replication in hive that are taking long to > > run and hence more often than not timeout as part of the batch they form. > > All these tests are in org.apache.hadoop.hive.ql.parse package. I tried > to > > skipBatching for these tests by changing the master-mr2.properties by > > adding these test classes to the property > > "ut.itests.hive-unit.skipBatching", however that does not seem to work > as > > the tests are still batched and in test on my patch i see "did not > produce > > a TEST-*.xml file (likely timed out) (batchId=244)" > > > > does anyone know how to skip batching for these tests ? > > > > Thanks > > anishek > > > >
