The GitHub Actions job "Tests" on airflow.git/fix-skip-to-latest has failed. Run started by GitHub user jedcunningham (triggered by jedcunningham).
Head commit for run: 9827701b2ac5c2edfa827b0b69ebc0ff98d2c7d5 / Jed Cunningham <[email protected]> Avoid re-emitting logical_date when previous data_interval is zero-length When a DAG is migrated from CronTriggerTimetable (point-in-time) to CronDataIntervalTimetable, the latest run's data_interval has ``start == end``. ``_DataIntervalTimetable.next_dagrun_info`` would then align ``start`` onto that same point, producing a new run whose ``logical_date`` collides with the existing one. The scheduler logged "run already exists; skipping dagrun creation" and looped until the next cron boundary, sometimes silently skipping a scheduled run. Detect the zero-length previous interval and advance ``start`` by one period so the next run gets a fresh ``logical_date``. Co-Authored-By: Claude Opus 4.7 (1M context) <[email protected]> Report URL: https://github.com/apache/airflow/actions/runs/25137160918 With regards, GitHub Actions via GitBox --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
