[
https://issues.apache.org/jira/browse/HIVE-14669?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16816355#comment-16816355
]
Hive QA commented on HIVE-14669:
--------------------------------
Here are the results of testing the latest attachment:
https://issues.apache.org/jira/secure/attachment/12965721/HIVE-14469.02.patch
{color:green}SUCCESS:{color} +1 due to 2 test(s) being added or modified.
{color:green}SUCCESS:{color} +1 due to 15938 tests passed
Test results:
https://builds.apache.org/job/PreCommit-HIVE-Build/16933/testReport
Console output: https://builds.apache.org/job/PreCommit-HIVE-Build/16933/console
Test logs: http://104.198.109.242/logs/PreCommit-HIVE-Build-16933/
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
{noformat}
This message is automatically generated.
ATTACHMENT ID: 12965721 - PreCommit-HIVE-Build
> Have the actual error reported when a q test fails instead of having to go
> through the logs
> -------------------------------------------------------------------------------------------
>
> Key: HIVE-14669
> URL: https://issues.apache.org/jira/browse/HIVE-14669
> Project: Hive
> Issue Type: Sub-task
> Reporter: Siddharth Seth
> Assignee: Laszlo Bodor
> Priority: Major
> Attachments: 01_mvn_out.png, 02_hive_log.png, HIVE-14469.01.patch,
> HIVE-14469.02.patch, Screen Shot 2019-04-11 at 4.54.41 PM.png
>
>
> QTest runs end up invoking CliDriver.processLine. This, in most cases,
> reports a numeric exit code - 0 for success. Non-zero for various different
> error types (which are defined everywhere in the code).
> Internally CliDriver does have more information via CommandResult. A lot of
> this is not exposed though. That's alright for the end user cli - (Command
> line tool translating the error to a code and message). However, it makes
> debugging very difficult for QTests - since the log needs to be looked at
> each time.
> Errors generated by the actual backend execution are mostly available to the
> client, and information about these should show up as well. (If it doesn't -
> we have a usability issues to fix).
> cc [~ekoifman]
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
