[jira] [Commented] (AIRFLOW-829) Reduce verbosity of successful Travis unit tests

["George Sakkis (JIRA)" <ji...@apache.org>]

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

George Sakkis commented on AIRFLOW-829:
---------------------------------------

+1, this has been bugging me since my first failed Travis run.

> Reduce verbosity of successful Travis unit tests
> ------------------------------------------------
>
>                 Key: AIRFLOW-829
>                 URL: https://issues.apache.org/jira/browse/AIRFLOW-829
>             Project: Apache Airflow
>          Issue Type: Improvement
>          Components: tests
>            Reporter: Jeremiah Lowin
>            Assignee: Jeremiah Lowin
>
> Unit tests are run with the -s flag, so every single test prints every single debug log -- including multiple lines for every single dependency check of every single operator in every single backfill iteration. This means that the full test suite log is so large it can not be downloaded from Travis (4MB cap!!). It is difficult at best and impossible at worst to identify failed tests.
> The -s flag should not be used with Travis. This way, successful tests will have their logging suppressed (or at least reduced) but failed tests will show captured log output, making identifying failures easy. Local testing can retain the -s flag by default.
> Note that all task logs are still printed because of how those logs are presented in the Airflow log.



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