Re: [DISCUSS] 26 Unit tests failing regularly

2018-02-07 Thread Prasanth Jayachandran
TestOperators failure is covered in HIVE-18653 Thanks Prasanth On Feb 7, 2018, at 9:01 AM, Vihang Karajgaonkar mailto:vih...@cloudera.com>> wrote: Thanks Eugene, Deepak and Sahil. I will take a look at the TestSSL ones. On Tue, Feb 6, 2018 at

Re: [DISCUSS] 26 Unit tests failing regularly

2018-02-07 Thread Vihang Karajgaonkar
Thanks Eugene, Deepak and Sahil. I will take a look at the TestSSL ones. On Tue, Feb 6, 2018 at 10:54 AM, Sahil Takiar wrote: > I can take a look at the Spark and Encryption ones. > > On Tue, Feb 6, 2018 at 10:38 AM, Deepak Jaiswal > wrote: > > > I already have JIRA for > > org.apache.hadoop.hi

Re: [DISCUSS] 26 Unit tests failing regularly

2018-02-06 Thread Sahil Takiar
I can take a look at the Spark and Encryption ones. On Tue, Feb 6, 2018 at 10:38 AM, Deepak Jaiswal wrote: > I already have JIRA for > org.apache.hadoop.hive.cli.TestMiniLlapLocalCliDriver. > testCliDriver[bucket_map_join_tez1] > > Will pick up these two, > > org.apache.hadoop.hive.cli.TestMiniL

Re: [DISCUSS] 26 Unit tests failing regularly

2018-02-06 Thread Deepak Jaiswal
I already have JIRA for org.apache.hadoop.hive.cli.TestMiniLlapLocalCliDriver.testCliDriver[bucket_map_join_tez1] Will pick up these two, org.apache.hadoop.hive.cli.TestMiniLlapCliDriver.testCliDriver[llap_smb] org.apache.hadoop.hive.cli.TestCliDriver.testCliDriver[auto_sortmerge_join_2] On 2/

Re: [DISCUSS] 26 Unit tests failing regularly

2018-02-06 Thread Eugene Koifman
I’ll take care of org.apache.hadoop.hive.ql.TestTxnNoBuckets.testCTAS (batchId=280) org.apache.hadoop.hive.ql.TestTxnNoBucketsVectorized.testCTAS (batchId=280) On 2/6/18, 9:54 AM, "Vihang Karajgaonkar" wrote: org.apache.hadoop.hive.ql.TestTxnNoBuckets.testCTAS (batchId=280) org.apache.h

[DISCUSS] 26 Unit tests failing regularly

2018-02-06 Thread Vihang Karajgaonkar
I see that the regularly failing unit tests on the master branch is slowly climbing up and its close to ~26 now. Many of these don't seem to be "flaky" test failures since they are consistently failing for a while with the same error message. Some of these can be fixed by a simple q.out update whil