Yea we looked at it before.. its tracked by HIVE-13223, caused by HIVE-13040.
Because it hangs these tests take 2 hours max now before they are killed, hence each run taking over 3 hours. Ashutosh is looking I believe, I havent had a chance to take a look myself. Szehon On Mon, Mar 28, 2016 at 2:28 PM, Siddharth Seth <ss...@apache.org> wrote: > There's several tests which are failing consistently. Should we disable > these and create blocker jiras to fix and enable thees for the next > release. The list of test is at the end of the mail. > > Also, each pre-commit run seems to be taking over 3 hours. Is this normal ? > Having test results come back 2 days after submitting a patch is not very > efficient. > > Thanks, > Sid > > TestSparkCliDriver-groupby3_map.q-sample2.q-auto_join14.q-and-12-more > - did not produce a TEST-*.xml file > > TestSparkCliDriver-groupby_map_ppr_multi_distinct.q-table_access_keys_stats.q-groupby4_noskew.q-and-12-more > - did not produce a TEST-*.xml file > > TestSparkCliDriver-join_rc.q-insert1.q-vectorized_rcfile_columnar.q-and-12-more > - did not produce a TEST-*.xml file > TestSparkCliDriver-ppd_join4.q-join9.q-ppd_join3.q-and-12-more - did > not produce a TEST-*.xml file > > TestSparkCliDriver-timestamp_lazy.q-bucketsortoptimize_insert_4.q-date_udf.q-and-12-more > - did not produce a TEST-*.xml file > > > org.apache.hadoop.hive.ql.exec.vector.expressions.TestVectorTimestampExpressions.testVectorUDFMonthString > > org.apache.hadoop.hive.ql.exec.vector.expressions.TestVectorTimestampExpressions.testVectorUDFMonthTimestamp > > org.apache.hadoop.hive.ql.exec.vector.expressions.TestVectorTimestampExpressions.testVectorUDFYearString > > org.apache.hadoop.hive.ql.exec.vector.expressions.TestVectorTimestampExpressions.testVectorUDFYearTimestamp >
