potiuk opened a new pull request, #67170: URL: https://github.com/apache/airflow/pull/67170
The default per-test timeout in core-integration CI is 60s (set by breeze via `--setup-timeout` / `--execution-timeout` / `--teardown-timeout`, default in `dev/breeze/src/airflow_breeze/commands/testing_commands.py:547`). The heavy fixture `dag_execution_for_testing_metrics` starts a real scheduler + apiserver, triggers a DAG, waits up to 90s for the run to finish, plus a 10s sleep for span_status processing. Happy-path timings we see in CI cluster around ~38s but the upper tail brushes against 60s. `test_dag_execution_succeeds` already has `@pytest.mark.execution_timeout(90)`. Its two siblings sharing the same fixture (`test_export_legacy_metric_names` and `test_export_metrics_during_process_shutdown`) were missing the marker, so they failed the moment one parametrize variant ticked past 60s — saw that in https://github.com/apache/airflow/actions/runs/26086088389/job/76701766269 (60.01s, missed by 0.01s). Aligns those two tests with the existing 90s budget. No behavior change. --- ##### Was generative AI tooling used to co-author this PR? - [X] Yes — Claude Opus 4.7 (1M context) Generated-by: Claude Opus 4.7 (1M context) 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]
