jeremiahishere commented on issue #41894: URL: https://github.com/apache/airflow/issues/41894#issuecomment-2326974576
It is failing in test for us. Production is not failing because the dag execution dates are based on the current time. It started failing when upgrading from airflow 2.6 to 2.7. I would love to be given the time to rewrite four years of test fixtures but I don't think that is going to happen. Should I expect this behavior in main or the v2-10-stable branch? I see roughly the same code here: https://github.com/apache/airflow/blob/main/airflow/models/dag.py#L3786-L3791 What is the use case where this code works as intended, deleting the previous dagrun and creating a new one? Is there something special about the test environment that skips loading the ab_user table metadata? Is there a different place to patch that will be easier to maintain as we upgrade across versions? -- 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]
