DanielLeens commented on PR #11077: URL: https://github.com/apache/seatunnel/pull/11077#issuecomment-5575009146
CI status (maintainer triage): the Build on `343205baa` finished with 6 failures + 2 cancellations, none related to this PR's diff (`seatunnel-api/.../multitablesink/*`, `connector-file-base` only): - `paimon-connector-it (8)`: cancelled after hitting its 180-minute budget - `PaimonIT` hung (repeating idle CoordinatorService thread-pool dumps with `runningJobCount: 1`, no progress for 2+ hours). This matches this session's already-documented pre-existing Paimon classloader/engine hang, unrelated to multi-table sink writer sharing. - `kudu-connector-it (11)`: cancelled after ~1.5h (its JDK 8 sibling passed in 25 min) - looks like a second instance of the same class of hang in a different connector, still zero overlap with this PR's files. - `transform-v2-it-part-1 (8)`: `TestFilterRowKindIT` - the still-unfixed #12116 (not #11995, which is already merged into this branch and doesn't cover this root cause). - `rocketmq-connector-it (11)`: known broker double-identity race, #12115, unmerged. - `all-connectors-it-4 (8)`: `EdgeSocketMysql8_4IT.testEdgeSocketCommitWatermarkAdvances` - Runtime error in an unrelated connector (edge-socket + MySQL watermark test). - `jdbc-connectors-it-part-6 (8)`: `JdbcHanaIT` - Testcontainers `ContainerLaunchException` (SAP HANA container failed to start) - infra, not code. - `doris-connector-it (11)`: `DorisSchemaChangeIT.testDorisWithSchemaEvolutionCase` - `ConditionTimeout` at `assertTableStructureAndData`; this PR touches zero Doris files, consistent with the general Doris-container instability already tracked elsewhere. - `Dead links`: the same repo-wide broken external link hit on other unrelated PRs today. No open code-level blockers (standing DanielLeens `APPROVED` at the pre-merge head still holds). This PR has now cleared two full CI rounds with failures that never overlap and never touch its own diff - recommend treating as ready for human/committer review even if a fully green run doesn't materialize, given the demonstrated unrelated-flake rate in this environment right now. Retriggering once more. -- 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]
