Re: Failing tests

[Alessandro Solimando]

Thanks Peter for taking care of this, I can confirm that "master" is good
now!

On Wed, 16 Mar 2022 at 12:30, Peter Vary  wrote:

> The tests should be green now...
>
> > On 2022. Mar 15., at 14:45, Stamatis Zampetakis 
> wrote:
> >
> > Hello,
> >
> > +1 to everything Peter said.
> >
> > Moreover a few other things/reminders which could make our life easier.
> >
> > No commits/merges over broken master.
> >
> > If there is a non-flaky failure in master then whoever notices it first,
> > please create a JIRA and add any relevant info. This will notify everyone
> > that there is a problem and it will also avoid having multiple people
> > looking at it.
> >
> > If there is failure in master or during precommit tests that seems to be
> > intermittent please run the flaky checker job [1]. If the result shows
> it's
> > flaky, log a JIRA and raise a PR disabling the test if there is no quick
> > fix available.
> >
> > Rerun precommit tests before merging a pull request if the latest
> precommit
> > run is old (e.g., greater than 72h).
> >
> > Best,
> > Stamatis
> >
> > [1] http://ci.hive.apache.org/job/hive-flaky-check/
> >
> >
> > On Mon, Mar 14, 2022 at 9:31 PM Peter Vary 
> > wrote:
> >
> >> If I remember correctly the decision was to not to merge changes with
> >> failing PreCommit tests.
> >>
> >> Lately, because of a mistake where the change was only partially merged,
> >> we had a failing test.
> >> I have tried to fix this issue and confirm it by rerunning the tests,
> but
> >> the check failed again. Now it failed with some different tests,
> because in
> >> the meantime there were some more failing tests were committed to
> master in
> >> the meantime.
> >>
> >> I think it would be good to stick to the previous decision and we should
> >> only commit changes if all of the tests are green. Also if there are
> some
> >> issues then it would be good to take the time to fix the failures or
> revert
> >> the changes causing the issues.
> >>
> >> Thanks,
> >> Peter
> >>
> >>
> >>
>
>

Re: Failing tests

[Peter Vary]

The tests should be green now...

> On 2022. Mar 15., at 14:45, Stamatis Zampetakis  wrote:
> 
> Hello,
> 
> +1 to everything Peter said.
> 
> Moreover a few other things/reminders which could make our life easier.
> 
> No commits/merges over broken master.
> 
> If there is a non-flaky failure in master then whoever notices it first,
> please create a JIRA and add any relevant info. This will notify everyone
> that there is a problem and it will also avoid having multiple people
> looking at it.
> 
> If there is failure in master or during precommit tests that seems to be
> intermittent please run the flaky checker job [1]. If the result shows it's
> flaky, log a JIRA and raise a PR disabling the test if there is no quick
> fix available.
> 
> Rerun precommit tests before merging a pull request if the latest precommit
> run is old (e.g., greater than 72h).
> 
> Best,
> Stamatis
> 
> [1] http://ci.hive.apache.org/job/hive-flaky-check/
> 
> 
> On Mon, Mar 14, 2022 at 9:31 PM Peter Vary 
> wrote:
> 
>> If I remember correctly the decision was to not to merge changes with
>> failing PreCommit tests.
>> 
>> Lately, because of a mistake where the change was only partially merged,
>> we had a failing test.
>> I have tried to fix this issue and confirm it by rerunning the tests, but
>> the check failed again. Now it failed with some different tests, because in
>> the meantime there were some more failing tests were committed to master in
>> the meantime.
>> 
>> I think it would be good to stick to the previous decision and we should
>> only commit changes if all of the tests are green. Also if there are some
>> issues then it would be good to take the time to fix the failures or revert
>> the changes causing the issues.
>> 
>> Thanks,
>> Peter
>> 
>> 
>> 

Re: Failing tests

[Stamatis Zampetakis]

Hello,

+1 to everything Peter said.

Moreover a few other things/reminders which could make our life easier.

No commits/merges over broken master.

If there is a non-flaky failure in master then whoever notices it first,
please create a JIRA and add any relevant info. This will notify everyone
that there is a problem and it will also avoid having multiple people
looking at it.

If there is failure in master or during precommit tests that seems to be
intermittent please run the flaky checker job [1]. If the result shows it's
flaky, log a JIRA and raise a PR disabling the test if there is no quick
fix available.

Rerun precommit tests before merging a pull request if the latest precommit
run is old (e.g., greater than 72h).

Best,
Stamatis

[1] http://ci.hive.apache.org/job/hive-flaky-check/


On Mon, Mar 14, 2022 at 9:31 PM Peter Vary 
wrote:

> If I remember correctly the decision was to not to merge changes with
> failing PreCommit tests.
>
> Lately, because of a mistake where the change was only partially merged,
> we had a failing test.
> I have tried to fix this issue and confirm it by rerunning the tests, but
> the check failed again. Now it failed with some different tests, because in
> the meantime there were some more failing tests were committed to master in
> the meantime.
>
> I think it would be good to stick to the previous decision and we should
> only commit changes if all of the tests are green. Also if there are some
> issues then it would be good to take the time to fix the failures or revert
> the changes causing the issues.
>
> Thanks,
> Peter
>
>
>

Failing tests

[Peter Vary]

If I remember correctly the decision was to not to merge changes with failing 
PreCommit tests.

Lately, because of a mistake where the change was only partially merged, we had 
a failing test.
I have tried to fix this issue and confirm it by rerunning the tests, but the 
check failed again. Now it failed with some different tests, because in the 
meantime there were some more failing tests were committed to master in the 
meantime.

I think it would be good to stick to the previous decision and we should only 
commit changes if all of the tests are green. Also if there are some issues 
then it would be good to take the time to fix the failures or revert the 
changes causing the issues.

Thanks,
Peter

[jira] [Created] (HIVE-22740) Test failing tests with return path

[Miklos Gergely (Jira)]

Miklos Gergely created HIVE-22740:
-

 Summary: Test failing tests with return path 
 Key: HIVE-22740
 URL: https://issues.apache.org/jira/browse/HIVE-22740
 Project: Hive
  Issue Type: Bug
Reporter: Miklos Gergely






--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Created] (HIVE-19142) Umbrella: branch-3 failing tests

[Vineet Garg (JIRA)]

Vineet Garg created HIVE-19142:
--

 Summary: Umbrella: branch-3 failing tests
 Key: HIVE-19142
 URL: https://issues.apache.org/jira/browse/HIVE-19142
 Project: Hive
  Issue Type: Test
Reporter: Vineet Garg






--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Created] (HIVE-18091) Failing tests of itests/qtest-spark and itests/hive-unit on branch-1

[Daniel Voros (JIRA)]

Daniel Voros created HIVE-18091:
---

 Summary: Failing tests of itests/qtest-spark and itests/hive-unit 
on branch-1
 Key: HIVE-18091
 URL: https://issues.apache.org/jira/browse/HIVE-18091
 Project: Hive
  Issue Type: Bug
  Components: Test, Testing Infrastructure
Reporter: Daniel Voros
Assignee: Daniel Voros


Seen this while looking at ptest results for HIVE-17947 but is probably an 
older issue.

Tests under itests/qtest-spark and itests/hive-unit fail when trying to execute 
the download-spark plugin with:

{code}
[INFO]
[INFO] 
[INFO] Building Hive Integration - Unit Tests 1.3.0-SNAPSHOT
[INFO] 
[INFO]
[INFO] --- maven-enforcer-plugin:1.3.1:enforce (enforce-no-snapshots) @ 
hive-it-unit ---
[INFO]
[INFO] --- maven-antrun-plugin:1.7:run (download-spark) @ hive-it-unit ---
[INFO] Executing tasks

main:
 [exec] + /bin/pwd
 [exec] + BASE_DIR=./target
 [exec] + HIVE_ROOT=./target/../../../
 [exec] + DOWNLOAD_DIR=./../thirdparty
 [exec] + mkdir -p ./../thirdparty
 [exec] 
/home/hiveptest/35.192.99.254-hiveptest-0/apache-github-branch-1-source/itests/hive-unit
 [exec] + download 
http://d3jw87u4immizc.cloudfront.net/spark-tarball/spark-1.5.0-bin-hadoop2-without-hive.tgz
 spark
 [exec] + 
url=http://d3jw87u4immizc.cloudfront.net/spark-tarball/spark-1.5.0-bin-hadoop2-without-hive.tgz
 [exec] + finalName=spark
 [exec] ++ basename 
http://d3jw87u4immizc.cloudfront.net/spark-tarball/spark-1.5.0-bin-hadoop2-without-hive.tgz
 [exec] + tarName=spark-1.5.0-bin-hadoop2-without-hive.tgz
 [exec] + rm -rf ./target/spark
 [exec] + [[ ! -f ./../thirdparty/spark-1.5.0-bin-hadoop2-without-hive.tgz 
]]
 [exec] + tar -zxf ./../thirdparty/spark-1.5.0-bin-hadoop2-without-hive.tgz 
-C ./target
 [exec] + mv ./target/spark-1.5.0-bin-hadoop2-without-hive ./target/spark
 [exec] + cp -f ./target/../../..//data/conf/spark/log4j.properties 
./target/spark/conf/
 [exec] + sed '/package /d' 
/data/hiveptest/working/apache-github-branch-1-source/itests/../contrib/src/java/org/apache/hadoop/hive/contrib/udf/example/UDFExampleAdd.java
 [exec] sed: can't read 
/data/hiveptest/working/apache-github-branch-1-source/itests/../contrib/src/java/org/apache/hadoop/hive/contrib/udf/example/UDFExampleAdd.java:
 No such file or directory
 [exec] + javac -cp 
/data/hiveptest/working/maven/org/apache/hive/hive-exec/1.3.0-SNAPSHOT/hive-exec-1.3.0-SNAPSHOT.jar
 /tmp/UDFExampleAdd.java -d /tmp
 [exec] + jar -cf /tmp/udfexampleadd-1.0.jar -C /tmp UDFExampleAdd.class
 [exec] /tmp/UDFExampleAdd.class : no such file or directory
[INFO] 
[INFO] BUILD FAILURE
[INFO] 
[INFO] Total time: 8.376s
[INFO] Finished at: Mon Nov 06 22:29:39 UTC 2017
[INFO] Final Memory: 18M/241M
[INFO] 
[ERROR] Failed to execute goal 
org.apache.maven.plugins:maven-antrun-plugin:1.7:run (download-spark) on 
project hive-it-unit: An Ant BuildException has occured: exec returned: 1
[ERROR] around Ant part .. @ 4:141 in 
/home/hiveptest/35.192.99.254-hiveptest-0/apache-github-branch-1-source/itests/hive-unit/target/antrun/build-main.xml
{code}

{{mvn antrun:run@download-spark}} passes when run locally, so I guess it might 
be an issue with the way wer're executing ptests.

Full list of classes with the same error:

{code}
TestAcidOnTez
TestAdminUser
TestAuthorizationPreEventListener
TestAuthzApiEmbedAuthorizerInEmbed
TestAuthzApiEmbedAuthorizerInRemote
TestBeeLineWithArgs
TestCLIAuthzSessionContext
TestClearDanglingScratchDir
TestClientSideAuthorizationProvider
TestCompactor
TestCreateUdfEntities
TestCustomAuthentication
TestDBTokenStore
TestDDLWithRemoteMetastoreSecondNamenode
TestDynamicSerDe
TestEmbeddedHiveMetaStore
TestEmbeddedThriftBinaryCLIService
TestFilterHooks
TestFolderPermissions
TestHS2AuthzContext
TestHS2AuthzSessionContext
TestHS2ClearDanglingScratchDir
TestHS2ImpersonationWithRemoteMS
TestHiveAuthorizerCheckInvocation
TestHiveAuthorizerShowFilters
TestHiveHistory
TestHiveMetaStoreTxns
TestHiveMetaStoreWithEnvironmentContext
TestHiveMetaTool
TestHiveServer2
TestHiveServer2SessionTimeout
TestHiveSessionImpl
TestHs2Hooks
TestJdbcDriver2
TestJdbcMetadataApiAuth
TestJdbcWithLocalClusterSpark
TestJdbcWithMiniHS2
TestJdbcWithMiniMr
TestJdbcWithSQLAuthUDFBlacklist
TestJdbcWithSQLAuthorization
TestLocationQueries
TestMTQueries
TestMarkPartition
TestMarkPartitionRemote
TestMetaStoreAuthorization
TestMetaStoreConnectionUrlHook
TestMetaStoreEndFunctionListener
TestMetaStoreEventListener

[jira] [Created] (HIVE-17201) (Temporarily) Disable failing tests in TestHCatClient

[Mithun Radhakrishnan (JIRA)]

Mithun Radhakrishnan created HIVE-17201:
---

 Summary: (Temporarily) Disable failing tests in TestHCatClient
 Key: HIVE-17201
 URL: https://issues.apache.org/jira/browse/HIVE-17201
 Project: Hive
  Issue Type: Bug
  Components: HCatalog, Tests
Affects Versions: 3.0.0
Reporter: Mithun Radhakrishnan
Assignee: Mithun Radhakrishnan


This is with regard to the recent test-failures in {{TestHCatClient}}. 

While [~sbeeram] and I joust over the best way to rephrase the failing tests 
(in HIVE-16908), perhaps it's best that we temporarily disable the following 
failing tests:
{noformat}
org.apache.hive.hcatalog.api.TestHCatClient.testPartitionRegistrationWithCustomSchema
 (batchId=177)
org.apache.hive.hcatalog.api.TestHCatClient.testPartitionSpecRegistrationWithCustomSchema
 (batchId=177)
org.apache.hive.hcatalog.api.TestHCatClient.testTableSchemaPropagation 
(batchId=177)
{noformat}



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Created] (HIVE-16140) Stabilize few randomly failing tests

[Ashutosh Chauhan (JIRA)]

Ashutosh Chauhan created HIVE-16140:
---

 Summary: Stabilize few randomly failing tests
 Key: HIVE-16140
 URL: https://issues.apache.org/jira/browse/HIVE-16140
 Project: Hive
  Issue Type: Test
  Components: Testing Infrastructure, Tests
Reporter: Ashutosh Chauhan
Assignee: Ashutosh Chauhan


Golden file update for vector_between_in test and sort_before_diff for couple 
of Perf tests.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Created] (HIVE-14896) Stabilize golden files for currently failing tests

[Ashutosh Chauhan (JIRA)]

Ashutosh Chauhan created HIVE-14896:
---

 Summary: Stabilize golden files for currently failing tests
 Key: HIVE-14896
 URL: https://issues.apache.org/jira/browse/HIVE-14896
 Project: Hive
  Issue Type: Test
  Components: Tests
Reporter: Ashutosh Chauhan
Assignee: Ashutosh Chauhan


3 tests currently fail because of stats mismatch in golden files.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Re: Failing tests, precommit test runtimes

[Siddharth Seth]

Created HIVE-13402 to disable the tests. Have narrowed it down to 3 hanging
tests. From what I understand the TestVectorTimestampExpressions tests have
already been fixed.

On Tue, Mar 29, 2016 at 10:27 AM, Ashutosh Chauhan 
wrote:

> I agree with disabling these tests till we are able to fix it. Since bug
> seems to be in spark runtime, it may take a little while to fix it.
> Increased run time for QA till then would be waste of resources.
>
> Thanks,
> Ashutosh
>
> On Tue, Mar 29, 2016 at 9:06 AM, Siddharth Seth  wrote:
>
> > Thanks Szehon. Should we disable the tests while the issue is resolved.
> > There's a backlog of 17 patches - which will take over 2 days to run at
> > this point.
> > Also, HIVE-13365 ended up running for over 8 hours yesterday. Maybe we
> > should put a cap on max runtime for a single run. Anyone know how to do
> > this ?
> >
> > On Mon, Mar 28, 2016 at 3:05 PM, Szehon Ho  wrote:
> >
> > > 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 
> > 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
> > > >
> > >
> >
>

Re: Failing tests, precommit test runtimes

[Ashutosh Chauhan]

I agree with disabling these tests till we are able to fix it. Since bug
seems to be in spark runtime, it may take a little while to fix it.
Increased run time for QA till then would be waste of resources.

Thanks,
Ashutosh

On Tue, Mar 29, 2016 at 9:06 AM, Siddharth Seth  wrote:

> Thanks Szehon. Should we disable the tests while the issue is resolved.
> There's a backlog of 17 patches - which will take over 2 days to run at
> this point.
> Also, HIVE-13365 ended up running for over 8 hours yesterday. Maybe we
> should put a cap on max runtime for a single run. Anyone know how to do
> this ?
>
> On Mon, Mar 28, 2016 at 3:05 PM, Szehon Ho  wrote:
>
> > 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 
> 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
> > >
> >
>

Re: Failing tests, precommit test runtimes

[Siddharth Seth]

Thanks Szehon. Should we disable the tests while the issue is resolved.
There's a backlog of 17 patches - which will take over 2 days to run at
this point.
Also, HIVE-13365 ended up running for over 8 hours yesterday. Maybe we
should put a cap on max runtime for a single run. Anyone know how to do
this ?

On Mon, Mar 28, 2016 at 3:05 PM, Szehon Ho  wrote:

> 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  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
> >
>

Re: Failing tests, precommit test runtimes

[Szehon Ho]

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  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
>

Failing tests, precommit test runtimes

[Siddharth Seth]

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

[jira] [Created] (HIVE-12210) Fix a few failing tests

[Aleksei S (JIRA)]

Aleksei S created HIVE-12210:


 Summary: Fix a few failing tests
 Key: HIVE-12210
 URL: https://issues.apache.org/jira/browse/HIVE-12210
 Project: Hive
  Issue Type: Bug
Affects Versions: 2.0.0
Reporter: Aleksei S
Assignee: Aleksei S


The following tests fail after HIVE-11785 because of missing 
"serialization.escape.crlf true" property in the output.
{code}
org.apache.hadoop.hive.cli.TestCliDriver.testCliDriver_udf_explode
org.apache.hadoop.hive.cli.TestCliDriver.testCliDriver_udtf_explode
{code}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (HIVE-11830) LLAP: Fix failing tests in MiniLlapCluster

[Prasanth Jayachandran (JIRA)]

Prasanth Jayachandran created HIVE-11830:


 Summary: LLAP: Fix failing tests in MiniLlapCluster
 Key: HIVE-11830
 URL: https://issues.apache.org/jira/browse/HIVE-11830
 Project: Hive
  Issue Type: Sub-task
Reporter: Prasanth Jayachandran
Assignee: Prasanth Jayachandran


After HIVE-11776 commit, some tests are showing diffs and some are failing in 
llap. Following is the current state of failures

ql/src/test/results/clientpositive/llap/acid_vectorization_partition.q.out 
(query result ordering difference)
ql/src/test/results/clientpositive/llap/auto_join_nulls.q.out (Operator Id 
difference)
ql/src/test/results/clientpositive/llap/auto_sortmerge_join_6.q.out (explain 
output difference)
ql/src/test/results/clientpositive/llap/constprog_dpp.q.out (different plan. 
User explain vs regular explain)
ql/src/test/results/clientpositive/llap/explainuser_1.q.out (stats difference)
ql/src/test/results/clientpositive/llap/fileformat_mix.q.out (pre/post hook 
output difference)
ql/src/test/results/clientpositive/llap/identity_project_remove_skip.q.out 
(partition column value difference and hybridgrace join enabled)
ql/src/test/results/clientpositive/llap/insert1.q.out (stage ordering 
difference)
ql/src/test/results/clientpositive/llap/join0.q.java1.8.out (type of join 
difference and explain plan difference)
ql/src/test/results/clientpositive/llap/metadata_only_queries_with_filters.q.out
 (prehook difference and query result difference)
ql/src/test/results/clientpositive/llap/unionDistinct_1.q.out (stats difference)
ql/src/test/results/clientpositive/llap/vector_leftsemi_mapjoin.q.out (stats 
difference)
ql/src/test/results/clientpositive/llap/vector_multi_insert.q.out (stats 
difference)
ql/src/test/results/clientpositive/llap/vector_outer_join1.q.out (stats 
difference)
ql/src/test/results/clientpositive/llap/vector_outer_join2.q.out (stats 
difference)
ql/src/test/results/clientpositive/llap/vector_outer_join3.q.out (stats 
difference)
ql/src/test/results/clientpositive/llap/vector_outer_join4.q.out (stats 
difference)
Following queries failed to run in llap
metadataonly1.q
optimize_nullscan.q
union_view.q
vector_cast_constant.q (run in java 7 and java 8)
vector_decimal_precision.q
vector_left_outer_join3.q
vector_outer_join.q.out
vectorized_parquet_types.q.out
vectorized_timestamp_ints_casts.q.out



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)