SEZ9 commented on PR #12165: URL: https://github.com/apache/seatunnel/pull/12165#issuecomment-6486126320
Thanks @Vivek1106-04 for digging into the logs on run 40463705801. Your read of both non-green jobs (runner shutdown mid-job for `rocketmq-connector-it (17)`, job time limit for `all-connectors-it-4 (11)`, with no reported test failures in either) is consistent with the summary I had, which only showed the `cancelled`/`failure` states without a causal error. I am not going to treat that as a pass by inference, though, so the gate on `a932e27a7` stays open until the re-run lands. Keeping this PR at its current head while that is resolved is the right call; please do not push anything unless the re-run points at a real source problem. Concrete asks: - When attempt 2 finishes, post the link to the re-run here together with the outcome of those two jobs. If either job goes non-green again, please include the failing step/report rather than just the job status so we can tell infrastructure noise from a real regression. - Confirm the head is still `a932e27a7` at that point (or call out any new commit explicitly), so I know whether a re-read is needed or only the CI gate update. On #13052: agreed with the sequencing. Tracking the remaining `handleCoordinatorError` callers there, along with the Issues 2/3 items you mentioned, and opening that PR only after this one merges keeps this diff unchanged, which is what I want for the final pass. <!-- streview-comment:2108 --> -- 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]
