[
https://issues.apache.org/jira/browse/AIRFLOW-829?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jeremiah Lowin updated AIRFLOW-829:
-----------------------------------
Description:
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.
was:
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 but failed tests will show captured log output,
making identifying failures easy. Local testing can retain the -s flag by
default.
> 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)
