airflow-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Tim Swast (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (AIRFLOW-2674) BashOperator eats stdout and stderr logs
Date Fri, 26 Oct 2018 00:27:00 GMT

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

Tim Swast commented on AIRFLOW-2674:
------------------------------------

Might have been `airflow test`. I haven't noticed this issue lately. (I've definitely seen
logs from the BashOperator since I filed this bug)

> BashOperator eats stdout and stderr logs
> ----------------------------------------
>
>                 Key: AIRFLOW-2674
>                 URL: https://issues.apache.org/jira/browse/AIRFLOW-2674
>             Project: Apache Airflow
>          Issue Type: Bug
>          Components: operators
>            Reporter: Tim Swast
>            Priority: Minor
>             Fix For: 1.10.1
>
>
> I've noticed that when I use the BashOperator, I do not see output from the bash processes
in the task logs or even my machine's logs. This makes it difficult-to-impossible debug problems
in a BashOperator task.
> See [related StackOverflow question "Airflow BashOperator log doesn't contain full output"|https://stackoverflow.com/q/43400302/101923].
> Possibly related to https://issues.apache.org/jira/browse/AIRFLOW-1733



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Mime
View raw message