keemgdeok opened a new pull request, #74143: URL: https://github.com/apache/airflow/pull/74143
A deferred `KubernetesJobOperator` ignores `job_poll_interval`: the operator passes the value to `KubernetesJobTrigger`, but the trigger omits it when calling `AsyncKubernetesHook.wait_until_job_complete`, which then always polls every 10 seconds. For example, configuring a 60-second interval still produces a 10-second wait. Pass the existing trigger interval to the hook. The new regression test runs the actual async polling loop with mocked Kubernetes responses and sleep, covering 0.5-second and 60-second intervals while checking the completion event and Job result. Existing success/failure tests now expect the interval argument. The default remains 10 seconds. Validation on upstream base `79de1d4803941e7ba4a6361529cc7079bb36373e`: - On the earlier upstream base `402d7885`, both regression cases fail before the fix: the actual wait is 10 seconds. The trigger and hook source files are unchanged between that base and the final base above. - Job Trigger test module: 7 passed. - Kubernetes provider unit suite: 1,385 passed, 19 skipped (serial execution). - GKE Job operator/trigger subset: 19 passed, 17 deselected. - Regular and manual prek checks passed, including provider mypy; `git diff --check` passed. - Breeze selective-check completed. Its wider CI matrix, live-cluster/system tests, other Python/Airflow versions and performance measurements were not run locally. Tests used Breeze with the existing local Python 3.10 CI image and current checkout sources (`--skip-image-upgrade-check`). No new options, dependencies or unrelated changes are included. --- ##### Was generative AI tooling used to co-author this PR? - [X] Yes — Codex (GPT-6) Generated-by: Codex (GPT-6) 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]
