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

   Thanks for the retry update. I refreshed the job results successfully: the 
Maven-download lane `all-connectors-it-2` JDK 17 now passed. My earlier 
three-failure list is stale. The remaining failed jobs are Kafka JDK 17 
([128322026424](https://github.com/DanielLeens/seatunnel/actions/runs/41602572467/job/128322026424))
 and all-connectors-it-5 JDK 11 
([128322026890](https://github.com/DanielLeens/seatunnel/actions/runs/41602572467/job/128322026890));
 the overall run remains failed.
   
   The previous diagnostics identified a Kafka committed-offset timeout and 
TiDB setup failure, respectively. The proposed TiDB readiness fix #13269 is 
still open, and no merged fix for the Kafka timeout has been established, so a 
dev sync alone is not a demonstrated cure. Preserve the new lane diagnostics 
and resolve the fixture cause before another targeted run; no unrelated 
dependency change belongs in this checkpoint regression PR. My source 
conclusion remains clear, while current-head CI and independent maintainer 
review remain required. This is a changed-CI clarification, not another source 
review or new local execution.


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