DanielLeens commented on PR #11868: URL: https://github.com/apache/seatunnel/pull/11868#issuecomment-5459188917
CI record update, @JeremyXin — following up on my 2026-08-22 note again, since the `Build` check has since been rerun many more times (this fork run is now on attempt 18) without landing on a clean, unrelated-flake-free result yet. The most recent completed attempt on this exact head (`9b95505c7`) failed on two jobs, both again unrelated to this PR's Hazelcast join-port fix: - `unit-test (11, ubuntu-latest)`: `SeaTunnelClientTest.testGetMultiTableJobMetrics` — an assertion failure (`expected: <true> but was: <false>`) in an unrelated metrics-reporting test; nothing in this PR touches `seatunnel-engine-client` or job metrics. - `jdbc-connectors-it-part-6 (8, ubuntu-latest)`: `JdbcHanaIT` — a Testcontainers `ContainerLaunchException` failing to start the `saplabs/hanaexpress` image; a Docker/infra flake, unrelated to Hazelcast config or the test classes this PR modified. Neither failure touches `AbstractSeaTunnelServerTest`, `WorkerTagTest`, `OptionRulesApiTest`, or any Hazelcast join/port-count code path. My "Ready to merge" conclusion still stands technically — but at this point the pattern across 18 rerun attempts is a different unrelated flaky job failing each time rather than converging to green, which looks like general CI/Docker capacity churn on this run rather than something a rerun reliably fixes. I would not keep force-rerunning; instead, please flag this to a maintainer with write access so they can either merge on the strength of the code review once any one run comes back clean, or advise if there's a known infra issue affecting these jobs right now. -- 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]
