ashb opened a new issue #17046: URL: https://github.com/apache/airflow/issues/17046
As part of the work on AIP-39 we want to make it so that _every_ TaskInstance in the DB has DagRun. Now at "run time" this is already the case (baring the case where someone might delete a DagRun. Rare, now only possible by direct DB? I can't remember if Browse -> DagRuns allows deleting anymore or not) but in our tests this is far from the case There are countless examples of where the tests just directly create TaskInstances, without a matching DagRun. We need to fix that so that the tests reflect reality. - [ ] https://github.com/apache/airflow/pull/16889 is part of this -- creating a pytest fixture to reduce amount of duplication in tests - [ ] We probably also want to enforce foreign key constraints between DagRun and TaskInstance once we've done this (see also https://github.com/apache/airflow/pull/17030) -- 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]
