potiuk opened a new pull request, #67811: URL: https://github.com/apache/airflow/pull/67811
test_send_thread_safety assumed concurrent `send()` calls would be answered in thread-index order. But `send()` serializes the write+read under a lock and correlates responses FIFO, so the lock-acquisition order (and thus the order requests arrive) is non-deterministic — the test only passed when threads happened to take the lock in start order, and flaked under scheduling jitter (seen on the Tests (ARM) scheduled run). The parent side now reads each request off the socket and echoes a response for that exact request, so every thread reliably receives the response to its own message regardless of scheduling. The production code is unchanged — this is a test-only fix. Verified by running the test 40x with no failures. --- ##### Was generative AI tooling used to co-author this PR? - [X] Yes — Claude Code (Opus 4.8) Generated-by: Claude Code (Opus 4.8) 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]
