shahar1 opened a new pull request, #74187:
URL: https://github.com/apache/airflow/pull/74187
The OpenLineage system test Dag
`openlineage_schedule_multiple_cron_trigger_timetable_dag` used
`MultipleCronTriggerTimetable("21 13 29 2 4", "9 27 29 2 4", timezone="UTC")`.
Hour `27` is not a valid cron hour, so croniter raises `CroniterBadCronError`
whenever the Dag processor computes the next run, and it logs `Failed to fetch
run info ... for DAG
'openlineage_schedule_multiple_cron_trigger_timetable_dag'` on every re-parse.
This floods the logs of the OpenLineage e2e compatibility jobs.
The typo was introduced in #68664 and copied into the expected events by
#69212.
This PR changes the second expression to `9 17 29 2 4`, which keeps the
Dag's intent (two cron expressions that never trigger a run on their own during
the test), and updates the expected OpenLineage events to match the corrected
timetable.
Verified locally: croniter accepts the new expression,
`MultipleCronTriggerTimetable.next_dagrun_info` returns a run date instead of
raising, and the serialized timetable (`expressions`, `timetable_summary`)
matches the updated expected events file. Fast static checks pass.
related: #68664
related: #69212
---
##### Was generative AI tooling used to co-author this PR?
- [X] Yes — Claude Code (Fable 5.1)
Generated-by: Claude Code (Fable 5.1) following [the
guidelines](https://github.com/apache/airflow/blob/main/contributing-docs/05_pull_requests.rst#gen-ai-assisted-contributions)
--
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]
