DanielLeens commented on PR #11396: URL: https://github.com/apache/seatunnel/pull/11396#issuecomment-5459248548
Updating the CI status from my last review, where I noted the `Build` check on this exact commit (`31b49e6b7`) was "currently queued on the fork... nothing to diagnose yet." That run (`32680436515`) has since completed with `failure`, so there's now something concrete to report. I pulled the job logs rather than just reading the check name: the failures are five Doris E2E test classes (`DorisTimerFlushIT`, `DorisCDCSinkIT`, `DorisErrorIT`, `DorisCatalogIT`, `DorisMultiReadIT`), and every one of them fails the same way -- `org.testcontainers.containers.ContainerLaunchException: Timed out waiting for container port to open` while starting the `apache/doris:doris-all-in-one-2.1.0` testcontainer (one even failed one step earlier, on the image pull itself, with an `InterruptedException`). That's a container/runner-resource bootstrap issue in the Doris connector-it module, not a test assertion failure, and it has nothing to do with this PR's diff (`FixedChunkSplitter` / JDBC partition-column splitting) -- the Doris connector code path isn't touched here. From my source-review side there's still no open code blocker on this head. Given the failure signature looks like transient container/runner contention rather than a deterministic break, the lowest-cost next step is a plain rerun of the failed jobs; if it reproduces identically on a clean rerun, that would point to something more systemic on the runner side worth a separate look, but I wouldn't hold this PR on it either way since the failing module is outside this diff's blast radius. -- 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]
