potiuk opened a new pull request, #67067:
URL: https://github.com/apache/airflow/pull/67067

   
`tests/kubernetes_tests/test_other_executors.py::TestCeleryAndLocalExecutor::test_integration_run_dag_with_scheduler_failure`
   is occasionally flaky on ARM CI — the scheduler is killed immediately after
   `start_job_in_kubernetes`, so the post-restart scheduler sometimes has to
   handle the very first scheduling step itself before the 40-second
   `monitor_task` timeout expires. `push` stays in `queued` for the full 40s
   and the test fails with `assert 'queued' == 'success'`.
   
   Two adjustments:
   
   1. **Before killing the scheduler**, wait until the `push` task instance has
      reached a `queued`-or-later state via a new `wait_until_task_in_executor`
      helper. The original scheduler has already handed the task to the
      executor, so the post-restart scheduler only needs to drive the
      downstream dependency for `puller`, not pick up `push` from scratch.
   2. **Bump** the post-restart `monitor_task` timeouts from 40 s → 120 s. The
      previous "fail fast if failing" budget races with scheduler-loop warm-up
      under load; 120 s is still quick on a real bug but gives headroom for
      the legitimate cases.
   
   This is the residual flake left after #46502 — the `kubectl rollout status`
   wait fixed the worst of it, but the race between "pod is running" and
   "scheduler loop is actually scheduling" remained. Reopens the spirit of
   #45145.
   
   Observed failing CI job: 
https://github.com/apache/airflow/actions/runs/25973707142/job/76353251911
   
   ---
   
   ##### 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]

Reply via email to