[jira] [Resolved] (HIVE-25618) Stack trace is difficult to find when qtest fails during setup/teardown

["Stamatis Zampetakis (Jira)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/HIVE-25618?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Stamatis Zampetakis resolved HIVE-25618.
----------------------------------------
    Fix Version/s: 4.0.0
       Resolution: Fixed

Fixed in [d521f149fade25f74e7ca28fa399103684a80580|https://github.com/apache/hive/commit/d521f149fade25f74e7ca28fa399103684a80580]. Thanks for the reviews [~asolimando], [~kgyrtkirk]!

> Stack trace is difficult to find when qtest fails during setup/teardown
> -----------------------------------------------------------------------
>
>                 Key: HIVE-25618
>                 URL: https://issues.apache.org/jira/browse/HIVE-25618
>             Project: Hive
>          Issue Type: Improvement
>          Components: Testing Infrastructure
>            Reporter: Stamatis Zampetakis
>            Assignee: Stamatis Zampetakis
>            Priority: Minor
>              Labels: pull-request-available
>             Fix For: 4.0.0
>
>          Time Spent: 50m
>  Remaining Estimate: 0h
>
> When a qtest fails while executing one of the setup/teardown methods of a CLI driver ([CliAdapter|https://github.com/apache/hive/blob/3e37ba473545a691f5f32c08fc4b62b49257cab4/itests/util/src/main/java/org/apache/hadoop/hive/cli/control/CliAdapter.java#L36] and its subclasses):
> {code:java}
>   public abstract void beforeClass() throws Exception;
>   public abstract void setUp();
>   public abstract void tearDown();
>   public abstract void shutdown() throws Exception;
> {code}
> the original stack trace leading to the failure cannot be found easily. 
> Maven console shows a stack trace which doesn't correspond to the actual exception causing the problem but another one which in most cases does not contain the original cause. 
> The original stack trace is not displayed in the maven console and it is not in the {{target/tmp/logs/hive.log}} either. At the moment it goes to {{target/surefire-reports/...-output.txt}}. 
> The developer needs to search in 2-3 places and navigate back and forth to the code in order to find what went wrong.
> Ideally the stack trace from the original exception should be printed directly in maven console. 



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