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

Stamatis Zampetakis reassigned HIVE-29008:
------------------------------------------

    Assignee: Stamatis Zampetakis

> CI logs do not display information about test execution
> -------------------------------------------------------
>
>                 Key: HIVE-29008
>                 URL: https://issues.apache.org/jira/browse/HIVE-29008
>             Project: Hive
>          Issue Type: Bug
>          Components: Build Infrastructure, Testing Infrastructure
>            Reporter: Stamatis Zampetakis
>            Assignee: Stamatis Zampetakis
>            Priority: Major
>
> Locally, when we run tests via maven we usually see the following INFO 
> messages in the console.
> {noformat}
> [INFO] -------------------------------------------------------
> [INFO]  T E S T S
> [INFO] -------------------------------------------------------
> [INFO] Running org.apache.hadoop.hive.ql.exec.vector.TestDateColumnVector
> [INFO] Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.198 
> s -- in org.apache.hadoop.hive.ql.exec.vector.TestDateColumnVector
> [INFO] 
> [INFO] Results:
> [INFO] 
> [INFO] Tests run: 2, Failures: 0, Errors: 0, Skipped: 0
> [INFO] 
> {noformat}
>  The output is very useful for various reasons and in particular to know the 
> status of the current test that is running. This is even more important in CI 
> where intermittent failures may arise since we want an easy way to determine 
> which test was run at each point in time.
> In the [past|https://ci.hive.apache.org/job/hive-precommit/job/master/2334/], 
> this information was present in every CI run and we could easily see the test 
> that is currently running in each split. However, after upgrading the 
> maven-surefire-plugin to 3.5.1 (HIVE-28519) this information was lost and is 
> not present in the CI output/logs 
> [anymore|https://ci.hive.apache.org/job/hive-precommit/job/master/2548/].



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to