DanielLeens commented on PR #11727: URL: https://github.com/apache/seatunnel/pull/11727#issuecomment-5552701678
## CI triage on `a30a0bd7b` (run still in progress — no retrigger until it completes) Three jobs have failed so far. Each traced from its own log rather than assumed: 1. **`doris-connector-it (8)` — `DorisErrorIT.testDoris` @ `DorisErrorIT.java:85`.** The pinned-frame assertion; stderr shows `DorisStreamLoad.stopLoad` → `Doris-01 stream load error` ← `UnknownHostException: doris_e2e`. Docker teardown race in dev's test (same as #11503). Source fix: #12114 (test-only). 2. **`doris-connector-it (11)` — `DorisSchemaChangeIT.testDorisWithSchemaEvolutionCase` @ `:255`.** `assertIterableEquals` on `select * … order by id` differed at row `[9]`: source id `164`, sink id `173` — the sink was still missing the 164–172 range when the 60 s post-DDL window expired. The same log shows 60× `Doris-01 stream load error` retries during the schema-evolution phase, i.e. stream-load retry lag, not data loss (the test cancels the job on timeout so final convergence is unobservable). Timing flake in dev's test; first sighting — on the recurrence watchlist. 3. **`all-connectors-it-7 (11)` — `PostgresCDCIT.testPostgresCdcSnapshotOnlyAndCommittedOffsetStartupModes` @ `:625`.** After `restoreJob` of the committed-offset job (`7942339021350665806`) the job deployed and ran normally — `SCHEDULED → DEPLOYING → RUNNING`, both tasks started, slot active, WAL streaming — for the full 3-minute window, but the post-restore insert (id 15) never reached the sink, and the test then cancelled it (`end with state CANCELED`). That is exactly open issue #11847 (committed-offset restore skips a row when the slot LSN advances past it), with fix #11864 still open. Relevant to this PR's review: the `BlockingWorker` start-latch change is on the *failure-to-start* path, which never fired here — tasks deployed and started cleanly — so this is not attributable to the diff. None of the three touch files in this PR's diff (`TaskExecutionService` + tests). Plan: once the run completes I'll retrigger; 1 clears when #12114 lands and is synced, 3 will keep recurring intermittently until #11864 lands. -- 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]
