DanielLeens commented on PR #11077: URL: https://github.com/apache/seatunnel/pull/11077#issuecomment-5549703776
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. This branch's current head (`975962f1e`) already contains that commit (confirmed via GitHub compare: 0 commits behind bbfc188e6), so the currently-running CI on this PR should no longer hit this specific flake. See #11458's [2026-09-04 CI run](https://github.com/apache/seatunnel/runs/100966104650) for concrete evidence of `rocketmq-connector-it` passing on both JDK 8/11 legs with this same fix. 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]
