drill-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Paul Rogers (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (DRILL-5053) Remove excessive output from unit test cases
Date Mon, 21 Nov 2016 03:28:58 GMT

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

Paul Rogers commented on DRILL-5053:
------------------------------------

{{org.apache.drill.exec.DrillSeparatePlanningTest#testPlanning}} dumps its output to stdout,
then ignores the row count. Modify the test to use the (commented out) silent listener, and
verify the output row count.

> Remove excessive output from unit test cases
> --------------------------------------------
>
>                 Key: DRILL-5053
>                 URL: https://issues.apache.org/jira/browse/DRILL-5053
>             Project: Apache Drill
>          Issue Type: Improvement
>    Affects Versions: 1.8.0
>            Reporter: Paul Rogers
>            Assignee: Paul Rogers
>            Priority: Minor
>
> Drill's maven build runs a wide variety of unit tests. Unfortunately, many tests produce
very verbose output, sometimes in lieu of checking results, making it hard to determine which
test actually fails.
> The ultimate goal is to run the following and have very little output:
> {code}
> mvn clean install -q
> {code}
> Specific issues will appear below as comments.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message