davidzollo commented on PR #11556: URL: https://github.com/apache/seatunnel/pull/11556#issuecomment-5323461794
Diagnosis of the two `updated-modules-integration-test-part-1` failures at head `506e295e3037` (run 31962112336, identical on JDK 8 and 11) — they have different causes: **1. `testPostgresCdcBackfillsConcurrentChangesDuringSnapshot` (30s ConditionTimeout at the lock-wait assertion) — test-design bug, fixed by the commit just pushed (2512249c71c).** The blocking job future plus the three gate-blocked DML futures all ran on `ForkJoinPool.commonPool()`, which has only three workers on the 4-vCPU GitHub runners (parallelism = nproc - 1). Demand was 4, so the third DML never started, `countSourceChangesWaitingForTableLock >= 3` could mathematically never pass, and the test always timed out after 30s — deterministically on CI, while passing on developer machines with more cores. The fix pins those futures to a dedicated 4-thread pool; no assertions changed. **2. `testPostgresCdcSnapshotOnlyAndCommittedOffsetStartupModes` (0-vs-1 rows after savepoint restore) — not caused by this PR; tracked in #11847.** The restored committed-offset job emitted zero rows while the slot's committed LSN advanced past the post-savepoint row's commit LSN (permanent silent loss). The test method is byte-identical to dev's, none of this PR's deltas are reachable on that path (all gated on exactly-once and/or INITIAL startup), and the same scenario passed 3/3 on this PR before the `86bcff279f6` dev merge and failed 2/2 after. Full LSN timeline and analysis in #11847. Until that is resolved, expect this one test to stay red here; a plain rerun is unlikely to help. -- 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]
