[ 
https://issues.apache.org/jira/browse/HIVE-23201?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17088382#comment-17088382
 ] 

Hive QA commented on HIVE-23201:
--------------------------------



Here are the results of testing the latest attachment:
https://issues.apache.org/jira/secure/attachment/13000596/HIVE-23201.5.patch

{color:red}ERROR:{color} -1 due to no test(s) being added or modified.

{color:red}ERROR:{color} -1 due to 2 failed/errored test(s), 17130 tests 
executed
*Failed tests:*
{noformat}
org.apache.hadoop.hive.cli.TestCliDriver.testCliDriver[timestamptz_2] 
(batchId=37)
org.apache.hive.hcatalog.templeton.TestConcurrentJobRequestsThreadsAndTimeout.ConcurrentListJobsVerifyExceptions
 (batchId=138)
{noformat}

Test results: 
https://builds.apache.org/job/PreCommit-HIVE-Build/21816/testReport
Console output: https://builds.apache.org/job/PreCommit-HIVE-Build/21816/console
Test logs: http://104.198.109.242/logs/PreCommit-HIVE-Build-21816/

Messages:
{noformat}
Executing org.apache.hive.ptest.execution.TestCheckPhase
Executing org.apache.hive.ptest.execution.PrepPhase
Executing org.apache.hive.ptest.execution.YetusPhase
Executing org.apache.hive.ptest.execution.ExecutionPhase
Executing org.apache.hive.ptest.execution.ReportingPhase
Tests exited with: TestsFailedException: 2 tests failed
{noformat}

This message is automatically generated.

ATTACHMENT ID: 13000596 - PreCommit-HIVE-Build

> Improve logging in locking
> --------------------------
>
>                 Key: HIVE-23201
>                 URL: https://issues.apache.org/jira/browse/HIVE-23201
>             Project: Hive
>          Issue Type: Improvement
>            Reporter: Marton Bod
>            Assignee: Marton Bod
>            Priority: Major
>         Attachments: HIVE-23201.1.patch, HIVE-23201.1.patch, 
> HIVE-23201.2.patch, HIVE-23201.2.patch, HIVE-23201.3.patch, 
> HIVE-23201.4.patch, HIVE-23201.5.patch, HIVE-23201.5.patch
>
>
> Currently it can be quite difficult to troubleshoot issues related to 
> locking. To understand why a particular txn gave up after a while on 
> acquiring a lock, you have to connect directly to the backend DB, since we 
> are not logging right now which exact locks the txn is waiting for.



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

Reply via email to