SEZ9 commented on PR #12366: URL: https://github.com/apache/seatunnel/pull/12366#issuecomment-6594381847
Following up on the CI point from my last comment (Build #27: `engine-v2-it (11, ubuntu-latest)` failing, `all-connectors-it-3 (17, ubuntu-latest)` cancelled at the 2h30m limit). Since then the head has moved. The automated review reports that `bc4270b53320c83842b07044ec823f5c3e0b31a7` had [Build](https://github.com/apache/seatunnel/runs/123362861435)=SUCCESS but was content-conflicting with `dev`, and that the new head `57b700f1559cbae9bd7bec156a4002dd7c589369` is a plain merge of current `dev`, 0 commits behind and mergeable, with Java code and tests byte-identical to `bc4270b5`. Thanks for resolving the conflict with a plain merge – that keeps the history easy to follow. Remaining asks on this point: 1. The green Build on `bc4270b5` does not cover the merge head. Please make sure the required checks run on `57b700f1559cbae9bd7bec156a4002dd7c589369` and let me know the outcome of `engine-v2-it (11, ubuntu-latest)` and `all-connectors-it-3 (17, ubuntu-latest)` specifically. 2. If `engine-v2-it` still fails on the new head, please paste the failing test name and the relevant log excerpt so we can tell whether it is tied to the routing/partitioner change or to the upstream issue tracked in #12316 that I mentioned previously. 3. If `all-connectors-it-3` hits the 2h30m limit again, please note that too; a rerun is fine if it looks like a flaky/timeout case rather than a real failure. I'll re-check the PR once the checks on the new head have finished. <!-- streview-comment:2250 --> -- 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]
