vatsrahul1001 commented on code in PR #72946: URL: https://github.com/apache/airflow/pull/72946#discussion_r3989935740
########## RELEASE_NOTES.rst: ########## @@ -6441,6 +6645,17 @@ You can achieve it also by installing airflow with ``[celery]``, ``[cncf.kuberne Users who base their images on the ``apache/airflow`` reference image (not slim) should be unaffected - the base reference image comes with all the three providers installed. +``DAG.test()`` now returns a ``DagRun`` and no longer stops at the first task failure (#32820) +"""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""" +This was an undocumented side effect of adding support for setup/teardown tasks in mapped task +groups. Previously, ``DAG.test()`` returned ``None``, and if any task raised an exception, the +whole test run stopped immediately without running the DAG's other schedulable tasks. Now, +``DAG.test()`` returns the ``DagRun`` it executed, and a failing task no longer aborts the run: +the remaining tasks keep running according to their trigger rules, just like in a real scheduled +run. This makes it possible to use ``DAG.test()`` to test DAGs where a task is expected to fail +but downstream tasks with a different trigger rule (or a parallel mapped task group) should still +run, without having to fall back to the ``DebugExecutor``. + Review Comment: https://github.com/apache/airflow/pull/72777 -- 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]
