potiuk opened a new pull request #19862: URL: https://github.com/apache/airflow/pull/19862
It used to be that the backfill job deadlocked when a task had "depends_on_past" set. This was because it depended on past, non-existing and not succesful task. You needed to set `ignore_first_depends_on_past' set in order to avoid the deadlock. This test was quarantined but I think the behaviour has changed. It looks like currently Airflow behaves differently: when checking dependencies, it actually retrieves the previous dag-run and if there is none available it does not deadlock no matter if depends_on_past is set. That makes much more sense and likely was fixed during the recent changes involved in timetable implementation. This PR updates the tests to show that backfill will behave properly, regardless from `ignore_first_depends_on_past`. Fixes: #14755 <!-- Thank you for contributing! Please make sure that your code changes are covered with tests. And in case of new features or big changes remember to adjust the documentation. Feel free to ping committers for the review! In case of existing issue, reference it using one of the following: closes: #ISSUE related: #ISSUE How to write a good git commit message: http://chris.beams.io/posts/git-commit/ --> --- **^ Add meaningful description above** Read the **[Pull Request Guidelines](https://github.com/apache/airflow/blob/main/CONTRIBUTING.rst#pull-request-guidelines)** for more information. In case of fundamental code change, Airflow Improvement Proposal ([AIP](https://cwiki.apache.org/confluence/display/AIRFLOW/Airflow+Improvements+Proposals)) is needed. In case of a new dependency, check compliance with the [ASF 3rd Party License Policy](https://www.apache.org/legal/resolved.html#category-x). In case of backwards incompatible changes please leave a note in [UPDATING.md](https://github.com/apache/airflow/blob/main/UPDATING.md). -- 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]
