abhijeets25012-tech commented on PR #74845: URL: https://github.com/apache/airflow/pull/74845#issuecomment-6341979685
Hi @jason810496 , could I get some guidance on the failing checks for PR #74845, which adds `on_success_succeed_dagrun` to teardown tasks? **CI failure:** [[Static checks — GitHub Actions](https://github.com/apache/airflow/actions/runs/39600877867/job/119229817743?pr=74845)](https://github.com/apache/airflow/actions/runs/39600877867/job/119229817743?pr=74845) (failed after 20 minutes). In addition, my focused `test_dagrun.py` run reported 15 failures, 290 passed, 2 skipped, and 1 xfailed. Several failures involve decorated and mapped operators not accepting or exposing `on_success_succeed_dagrun`, while another concerns the expected final DAG-run state. Could someone point me toward the intended implementation pattern for this option, particularly how it should propagate through decorated/mapped operators and interact with DAG-run state evaluation? I want to align the fix with Airflow's existing conventions rather than introduce a workaround that causes further regressions. Thanks for your guidance! -- 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: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
