DanielLeens commented on PR #11458: URL: https://github.com/apache/seatunnel/pull/11458#issuecomment-5549703430
The `rocketmq-connector-it` `MQClientException: CODE: 17 ... No topic route info in name server for the topic: test_topic_source` failure seen on this branch's earlier runs is a known Testcontainers startup-timing race (RocketMQ name-server route metadata not yet propagated when the test starts producing/consuming), unrelated to this PR's own diff. It's already fixed on `dev` via #12050 ([Fix][Zeta] Stabilize CI test isolation, merged 2026-09-04, commit bbfc188e6), which adds a bounded `waitForTopicRoute()` Awaitility poll in `RocketMqIT` before producing/asserting against `test_topic_source` / `test_topic` / `test_text_topic` / the restore-test topics, plus a related offset-sync timeout bump (30s -> 60s) to match the queue-count increase in the same PR. This branch's current head (`a71c68c42`) already contains that commit, and the [2026-09-04 CI run](https://github.com/apache/seatunnel/runs/100966104650) confirms both `rocketmq-connector-it` legs (JDK 8 and 11) passing. The `Build` failure on that same run comes from unrelated `doris-connector-it` and `jdbc-connectors-it-part-7` jobs. No action needed here for the RocketMQ flake specifically — flagging for visibility in case an older/unsynced run shows it again. -- 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]
