vatsrahul1001 opened a new pull request, #76117: URL: https://github.com/apache/airflow/pull/76117
Backport of #75030 to `v3-4-test`. ## Why `v3-4-test` CI is red on the core DB-test jobs — and therefore the rc2 sync PR #76068 — because the `Other` parallel test type deadlocks and times out the whole job (56-min total-test-timeout → exit 2). The culprit is `airflow-core/tests/unit/executors/test_local_executor.py::TestLocalExecutor::test_process_workloads_progresses_under_concurrent_result_refill`, the regression test added by #70545 (backported here as #74949). That test was flaky: it emitted 16 KiB result payloads for ~0.9 KiB workloads, which can close a two-pipe deadlock that the production drain-before-put fix is not meant to prevent at that ratio. It passes most of the time (so rc1's sync PR #75755 merged green on 2026-10-27) but deadlocks reliably under heavier parallel load. #75030 fixed the **test** — it uses result payloads smaller than a workload (512 B) and raises the workload count so it stays deterministic with the fix. Production `local_executor.py` is unchanged and is already byte-identical to `main`; this is a test-only change. #75030 merged to `main` on 2026-10-19 but was never labelled `backport-to-v3-4-test`, so auto-backport never carried it over (its parent #70545 was labelled and backported, leaving `v3-4-test` running the flaky test without its fix). This unblocks the 3.4.0rc2 sync. ## Verification Reproduced the deadlock on `v3-4-test` locally (parallel core-tests, sqlite backend, all six test types) — `Other` hangs on this exact test. With this cherry-pick applied the same run no longer deadlocks. The CI on this PR is the authoritative check. --- ##### Was generative AI tooling used to co-author this PR? - [x] Yes — Claude Code (Opus 4.8) Generated-by: Claude Code (Opus 4.8) -- 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]
