kaxil opened a new pull request, #36517:
URL: https://github.com/apache/airflow/pull/36517
**Motivation**:
Currently, when using `airflow dags test`, there is no easy way to know
programmatically if a DagRun fails since the state is not stored in DB. The way
to do know relies on log
dirrao commented on PR #36517:
URL: https://github.com/apache/airflow/pull/36517#issuecomment-1873176047
> I am a bit wondering why we add another CLI parameter. If the DAG test
fails and exit code 0 is returned I'd rather see this as a bug.
>
> Is there a reason adding a new CLI para
potiuk commented on PR #36517:
URL: https://github.com/apache/airflow/pull/36517#issuecomment-1873242002
Once concern is backwards compatibility (and I think that's where @kaxil's
solution came from).
But yeah, I think you are right @jscheffl @dirrao - probably return value is
not **
jscheffl commented on PR #36517:
URL: https://github.com/apache/airflow/pull/36517#issuecomment-1873268073
> Once concern is backwards compatibility (and I think that's where @kaxil's
solution came from).
>
> But yeah, I think you are right @jscheffl @dirrao - probably return value
i
kaxil commented on PR #36517:
URL: https://github.com/apache/airflow/pull/36517#issuecomment-1873817303
>I am a bit wondering why we add another CLI parameter. If the DAG test
fails and exit code 0 is returned I'd rather see this as a bug.
Yeah I tried to think more on it to keep back
kaxil commented on PR #36517:
URL: https://github.com/apache/airflow/pull/36517#issuecomment-1873821721
@jscheffl Done
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To un
kaxil merged PR #36517:
URL: https://github.com/apache/airflow/pull/36517
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: commits-unsubscr...@airflow.ap
