Dev-iL commented on PR #64972:
URL: https://github.com/apache/airflow/pull/64972#issuecomment-4230895455

   ## CI Timeout Investigation: 
`All-core:LowestDeps:14:3.12:Core...Serialization`
   
   ### Summary
   
   The CI job `All-core:LowestDeps:14:3.12:Core...Serialization` was cancelled 
after 1h5m (exceeding `TOTAL_TEST_TIMEOUT: 3600s`). This is a **pre-existing 
flake**, not caused by this PR's changes.
   
   ### Evidence
   
   **1. Only Python 3.12 affected**
   The same test group (`LowestDeps:Core...Serialization`) passed on Python 
3.10, 3.11, 3.13, and 3.14. Only the 3.12 run timed out.
   
   **2. "Other" group stuck at 63%**
   The "Other" test group reported "1 failed, 1093 passed, 12 skipped" at the 
12:47 mark and made no further progress until cancellation at 13:40. The PR 
adds ~8 tests — the hang is deep in pre-existing tests (1093+).
   
   **3. PR code is identical between force-pushes**
   Diffing the PR-specific files between commits 931fbf06 and 553c33ff (pre- 
and post-rebase) shows zero differences — only the rebased base changed.
   
   **4. Backend markers verified correct**
   - `BACKEND=sqlite` env var is set in LowestDeps CI (confirmed from logs)
   - `--backend` is NOT passed as a pytest CLI arg (`Extra pytest args: ()`)
   - `@pytest.mark.backend("sqlite")` → runs (BACKEND matches) ✓
   - `@pytest.mark.backend("postgres", "mysql")` → skipped (BACKEND doesn't 
match) ✓
   - No hang path through the backend marker logic
   
   **5. Upstream changes between force-pushes**
   The rebase picked up: `feat: restore os provider on core library (#64764)`, 
`Remove unused/dead code in migration utils (#64947)`, `Added plugins command 
to airflowctl (#64935)`, `Breeze: Show local reproduction commands (#63901)`. 
None of these touch the test infrastructure in a way that would cause a Python 
3.12-specific hang.
   
   ### Conclusion
   
   Most likely cause: a pre-existing flaky test in the "Other" group that hangs 
specifically on Python 3.12 (possibly a deadlock or resource contention issue). 
The PR's changes (AST-based migration checks + migration util tests) are not 
involved — they ran in a different test group and the PR files are 
byte-identical across the rebase.


-- 
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