DanielLeens commented on PR #11337: URL: https://github.com/apache/seatunnel/pull/11337#issuecomment-5319296745
Run `32041891318` on `d7ca6586` came back red; I read every failing job log before acting, and the failures split into two categories: - **Infra, not the PR**: `Dead links` 404'd on github.com blob URLs that demonstrably exist (`plugin-mapping.properties`, `seatunnel-dist/pom.xml` on dev), and all three `updated-modules-integration-test` failures died in `actions/setup-java` download with 429/503 before any test ran — GitHub was throttling/degraded in that window. Nothing to fix on our side; the new run retries these. - **Real test-timing flake, now fixed**: `unit-test (11, windows-latest)` failed `testCloseInterruptsInheritedStdoutWait` and `testConcurrentCloseStopsBufferedBatchEmission` — both on 5-second budgets that gate real python interpreter startup, which a loaded Windows runner can exceed on cold start alone. `f7dd2917b3` widens both waits to the 15s budget `pollUntilIOException` already uses for the identical arming wait in the same file. No assertion is changed or weakened — the tests prove the same conditions, they just stop racing a runner's process-spawn latency. Production code remains byte-identical to the green head `32ed4dfbba`. Build is running on the new head. -- 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]
