uranusjr commented on issue #51644: URL: https://github.com/apache/airflow/issues/51644#issuecomment-2969138202
I played around a bit. Assuming a fresh database… 1. `airflow dags test example_inactive_asset` immediately → fail 2. Trigger from UI with `airflow standalone` → success 3. `airflow dags test example_inactive_asset` after running `standalone` → success I think this is caused by the dag processor being responsible for collecting assets, and it does not kick in when you do `airflow dags test`. After you let the dag processor collect the assets, everything would work as expected. I’m not quite sure how to handle this. Should we do a round of dag collection when a dag is run from CLI (on the to-be-run dag)? Or do we just ignore all the assets when using `test` (and not emit an event at all—which might make sense instead since you probably wouldn’t expect a downstream to be triggered when testing a dag)? -- 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.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
