[GitHub] [airflow] dstandish removed a comment on issue #18473: CLI: `airflow dags test { dag w/ schedule_interval=None } ` error: "No run dates were found"

[GitBox <gi...@apache.org>]

dstandish removed a comment on issue #18473:
URL: https://github.com/apache/airflow/issues/18473#issuecomment-934621277


   > maybe eventually we should get rid of `airflow dags test` entirely and add a flag to `trigger` and `backfill` instead to make them block and emit logs to the CLI (i.o.w. allow the user to run them with `DebugExecutor` instead of the default `LocalExecutor`) to cover the use case. This would make more semantical sense because it'd be obvious to the user what kind of run they are requesting (backfill or manual), and it'd be easier to understand why a backfill does not trigger any runs at all.
   
   Yeah now that you mention it, `dags test` is not not super obvious that it's actually running the task.  One could think it is running _tests_ for the dag.
   
   For me, as an airflow user, I rarely use `airflow test` or debug executor. 
   
   When I use debug executor it's like this:
   


-- 
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-unsubscribe@airflow.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org