DanielLeens commented on PR #11503: URL: https://github.com/apache/seatunnel/pull/11503#issuecomment-5574568524
CI status (maintainer triage): the Build on `ff321c7b6` finished with 4 failures, all confirmed unrelated to this PR's diff: - `Dead links`: one broken external link (`https://github.com/apache/seatunnel-shade` in an unrelated Zeta deployment doc) - repo-wide, hit identically on other unrelated PRs' builds today. - `paimon-connector-it (8)`: `PaimonSinkCDCIT.testSinkWithIncompatibleSchema` - `ConditionTimeoutException` from the shared E2E harness's post-job thread-cleanup check (`SeaTunnelContainer.doExecuteJob`), waiting on an idle `st-multi-table-sink-writer-1` thread-pool worker parked in `getTask()`. Checked the full thread dump: it's a generic shutdown-timing flake in the shared multi-table-sink-writer thread pool, not the `applySchemaChange`/`RestoreTableSchemaEvent` path this PR actually touches (that branch isn't exercised by this test at all - no restore/failover involved). - `doris-connector-it (11)`: `DorisSchemaChangeIT.testDorisWithSchemaEvolutionCase` - Doris backend-internal error (`Can't find tablet id: 10170, maybe already dropped`, a C++ stack trace from Doris's own storage engine) plus a stream-load redirect failure. Server-side Doris container instability, unrelated to this PR's `DorisSinkWriter.applySchemaChange` change (same restore-only branch, not exercised here either). - `rocketmq-connector-it (11)`: the known broker double-identity race (tracked #12115, still unmerged). This is the second full attempt with zero failures overlapping between the two runs and zero connection to this PR's actual schema-restore-on-checkpoint logic. No open code-level blockers. Retriggered once more with an empty commit (`f77cdfa67`); if this comes back red again with more unrelated infra noise, recommend treating this as ready for merge despite non-green CI rather than continuing to retrigger indefinitely. -- 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]
