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

Hive QA commented on HIVE-13517:
--------------------------------



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

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

{color:red}ERROR:{color} -1 due to 1 failed/errored test(s), 10511 tests 
executed
*Failed tests:*
{noformat}
org.apache.hadoop.hive.cli.TestCliDriver.testCliDriver[comments] (batchId=35)
{noformat}

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

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

This message is automatically generated.

ATTACHMENT ID: 12860189 - PreCommit-HIVE-Build

> Hive logs in Spark Executor and Driver should show thread-id.
> -------------------------------------------------------------
>
>                 Key: HIVE-13517
>                 URL: https://issues.apache.org/jira/browse/HIVE-13517
>             Project: Hive
>          Issue Type: Bug
>          Components: Spark
>    Affects Versions: 1.2.1, 2.0.0
>            Reporter: Szehon Ho
>            Assignee: Sahil Takiar
>         Attachments: executor-driver-log.PNG, HIVE-13517.1.patch, 
> HIVE-13517.2.patch
>
>
> In Spark, there might be more than one task running in one executor. 
> Similarly, there may be more than one thread running in Driver.
> This makes debugging through the logs a nightmare. It would be great if there 
> could be thread-ids in the logs.



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

Reply via email to