DanielLeens commented on PR #12902: URL: https://github.com/apache/seatunnel/pull/12902#issuecomment-6655678197
Thanks @hutiefang76 for retrying and for the careful probe write-up. I checked [attempt 2](https://github.com/hutiefang76/seatunnel/actions/runs/41828185781/attempts/2): the two JDK 11 lanes now pass, and the only failure left is `all-connectors-it-5 (17, ubuntu-latest)`. It fails at the same place as before: `TiDBCDCIT.startUp:94` -> `TiDBTestBase.initializeTidbTable:213`, `CommunicationsException: Communications link failure ... has not received any packets from the server`, about 1 second after `Containers are started.` I don't think this is caused by your change: - This PR only touches the Protobuf compiler path (`CompileDescriptor` + `ProtobufConverterTest`). Nothing in the TiDB E2E, `seatunnel-e2e-common` or workflow files differs from dev. - On dev, the same `TiDBCDCIT` passed in the latest `all-connectors-it-5 (17)` Build (run 41866368355, 2026-11-04). - #12871 fails at the same TiDB setup step, and its retry on the unchanged head came back fully green. `initializeTidbTable` opens its first JDBC connection right after `Startables.deepStart` returns and does not retry, so a TiDB container that is slow to accept MySQL connections would fail the whole class. My guess is that it is an intermittent readiness problem, but the evidence here doesn't prove it. The cheapest next step is to rerun just that failed job once more (`gh run rerun 41828185781 --repo hutiefang76/seatunnel --job 127085101792`). Please don't sync dev or add retries or wait changes in this PR. If the job keeps failing, that points to a TiDB E2E readiness fix, which should go in its own PR. The source review conclusion is unchanged: no source blockers, and green CI on this head is the only remaining gate. -- 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]
