hive-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hive QA (JIRA)" <>
Subject [jira] [Commented] (HIVE-14669) Have the actual error reported when a q test fails instead of having to go through the logs
Date Fri, 12 Apr 2019 15:22:00 GMT


Hive QA commented on HIVE-14669:

Here are the results of testing the latest attachment:

{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:
Console output:
Test logs:

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

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
> -------------------------------------------------------------------------------------------
>                 Key: HIVE-14669
>                 URL:
>             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

View raw message