hive-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sahil Takiar (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HIVE-16309) Hive Test Commands failure should be printed in hive.log in addition to stderr
Date Tue, 28 Mar 2017 21:25:41 GMT

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

Sahil Takiar commented on HIVE-16309:
-------------------------------------

[~aihuaxu], [~vihangk1] could you review? This is an improvement to the test infra for running
HDFS encryption tests. When commands such as {{CRYPTO CREATE_KEY}} fail, the whole stack trace
is now printed out.

Test failures are all flaky tests:

HIVE-16320 - TestBeeLineDriver.testCliDriver[escape_comments]
HIVE-16256 - TestCliDriver.testCliDriver[comments]
HIVE-16312 - TestHCatClient.testTransportFailure

> Hive Test Commands failure should be printed in hive.log in addition to stderr
> ------------------------------------------------------------------------------
>
>                 Key: HIVE-16309
>                 URL: https://issues.apache.org/jira/browse/HIVE-16309
>             Project: Hive
>          Issue Type: Bug
>          Components: Test
>            Reporter: Sahil Takiar
>            Assignee: Sahil Takiar
>         Attachments: HIVE-16309.1.patch
>
>
> When the {{QTestUtil.executeTestCommand}} runs a test only command, and the command fails,
the exception info is printed to stdout rather than the log file. Printing out to the logs
file will better help debuggability of these failures.



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

Mime
View raw message