DanielLeens commented on PR #11077:
URL: https://github.com/apache/seatunnel/pull/11077#issuecomment-5551230213

   ## CI follow-up on the descoped head (`975962f`)
   
   `Build` finished red with 4 failing jobs: `transform-v2-it-part-1 (11)`, 
`rocketmq-connector-it (8 and 11)`, `doris-connector-it (11)`. Checked this 
PR's current file list first — none of `connector-rocketmq`, `connector-doris`, 
or `seatunnel-transforms-v2` appear in it at all (the diff is now just 
`multitablesink`/file-sink work plus docs), so none of these are inside this 
branch's own diff, unlike the DorisErrorIT situation I found on #11503 just now 
where the failing test was actually part of that PR's own changes.
   
   Spot-checked `rocketmq-connector-it (8)`: same `MQClientException: CODE: 17 
... No topic route info in name server for the topic: test_topic_source` 
pattern already tracked on #11458/#11077 as a known Testcontainers timing race 
(312 occurrences of the same message across retries in the log). Not re-tracing 
`doris-connector-it`/`transform-v2-it-part-1` individually to the same depth 
since the file-scope evidence is decisive here — none of the failing jobs' 
modules are anywhere in this PR's diff, so I'm confident classifying all 4 as 
unrelated to this branch's actual change without needing a job-by-job root 
cause for each.
   
   **Net: still no source-level blocker for this PR.** A job-level rerun should 
clear it; if it doesn't, that's evidence of broader CI flakiness independent of 
this change, not something to fix here.
   


-- 
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]

Reply via email to