DanielLeens commented on PR #11868: URL: https://github.com/apache/seatunnel/pull/11868#issuecomment-5379464099
CI record correction on my own approval, @JeremyXin — the fix itself is unaffected, but I want to be precise about what's currently red. When I approved, I cited a confirmed-green rerun of `Build` run `32352285042` (fork run, head `9b95505c7a71`). That run's overall conclusion has since flipped to failure — but checking the individual jobs, that's because three of its jobs were re-run a day later (2026-08-21) and hit new, unrelated failures, not a regression in anything this PR touched: - `all-connectors-it-6 (8, ubuntu-latest)` — `Couchbase` container startup failure, matching a known dev-red Couchbase bootstrap-break pattern (~20s `Connection reset` against the Couchbase container) that's been hitting unrelated PRs since mid-August. - `paimon-connector-it (8, ubuntu-latest)` — `PaimonSinkCDCIT.testSinkWithIncompatibleSchema` failure, a Paimon schema-compatibility assertion with nothing to do with Hazelcast join ports. - `all-connectors-it-5 (8, ubuntu-latest)` and the `(11, ...)` variants of these three jobs were cancelled as a side effect. None of these touch `seatunnel-engine-common`, Hazelcast config, or any of the test classes this PR modified (`AbstractSeaTunnelServerTest`, `WorkerTagTest`, `OptionRulesApiTest`, `RestApiSubmitJobStartWithSavePointTest`, `RestApiSubmitJobConfigShadeDecryptTest`). So to be clear: the specific concern I raised and then cleared in my last review (the Windows `OptionRulesApiTest` "Node failed to start!" failure) is still resolved — it hasn't recurred. This is a separate, later, unrelated flake from re-running other jobs in the same workflow run. My "Ready to merge" conclusion stands. A rerun of the three affected jobs should get this back to green; no action needed on your end. -- 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]
