danielnadean commented on PR #10583:
URL: https://github.com/apache/seatunnel/pull/10583#issuecomment-5317289643

   Update on the CI situation: the fresh run after yesterday's dev-sync cleared 
all three of the previously failing jobs (kafka, rocketmq, 
all-connectors-it-7), confirming those were environment flakes. The new run's 
only failure was a different one — `all-connectors-it-1 (8, ubuntu-latest)`, 
where `CouchbaseIT.startUp` died on a Testcontainers container-launch error 
(`unexpected end of stream` during the Couchbase HTTP bootstrap, 20s in). 
That's a docker-infrastructure flake, again unrelated to this PR's Javadoc-only 
diff.
   
   Since I can't re-run Actions on this fork, I've pushed another 
`upstream/dev` sync to the branch instead (4 new dev commits since yesterday, 
clean merge, the PR's diff is unchanged — still only the 
`MultiTableWriterRunnable` Javadoc). That keeps the branch current and 
retriggers CI as a side effect. If this run hits yet another unrelated 
container flake, a committer with fork-run access re-running just the failed 
job would be the cheaper path going forward.
   


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