DanielLeens commented on PR #11307: URL: https://github.com/apache/seatunnel/pull/11307#issuecomment-5551390864
CI update on this exact head (`169864a0be9`): the run I flagged as still queued/in-progress (`https://github.com/goutamadwant/seatunnel/actions/runs/33731860742`) has since completed — but as `cancelled`, not pass or fail. Looking at the job breakdown: 60 jobs succeeded, 10 were skipped as expected, and 0 jobs actually failed — 19 jobs were cancelled mid-run (e.g. `elasticsearch-connector-it`, `connector-redis-it (11)`, `mysql-cdc-connector-it`, `connector-file-sftp-it`), which reads like the whole workflow got cut off (very long total runtime, ~8.5h per the apache-side check) rather than any test actually failing, and none of the cancelled jobs are in the Spark/Druid area this PR's own diff touches. So there is still no negative signal against this PR's changes — just an inconclusive run. Could you retrigger the `Build` workflow on this head so we get one clean, complete run to close this out? Once that comes back green, I don't have any remaining source-level concerns from my last review. -- 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]
