DanielLeens commented on PR #12810: URL: https://github.com/apache/seatunnel/pull/12810#issuecomment-6473810492
Thanks for the contribution. The CI fact cited in my previous conclusion has changed; this follow-up updates that gate on the unchanged reviewed head, without issuing another full source review. Gate snapshot (2026-10-28T15:54:34+00:00), head `e637f1aeef8d3ef7d15050bddcf750c4a249a202`: [Build](https://github.com/apache/seatunnel/runs/122200458489) is `FAILURE`. The blocking jobs are [Run / unit-test (11, ubuntu-latest)](https://github.com/NganWave/seatunnel/actions/runs/40453802024/job/122023118795) `cancelled`; [Run / unit-test (17, windows-latest)](https://github.com/NganWave/seatunnel/actions/runs/40453802024/job/122023118817) `cancelled`; [Run / unit-test (11, windows-latest)](https://github.com/NganWave/seatunnel/actions/runs/40453802024/job/122023118851) `cancelled`; [Run / unit-test (17, ubuntu-latest)](https://github.com/NganWave/seatunnel/actions/runs/40453802024/job/122023118903) `cancelled`; [Run / all-connectors-it-4 (11, ubuntu-latest)](https://github.com/NganWave/seatunnel/actions/runs/40453802024/job/122023119046) `failure`; [Run / all-connectors-it-4 (17, ubuntu-latest)](https://github.com/NganWave/seatunnel/actions/runs/40453802024/job/122023119071) `failure`; [Run / all-connectors-it-2 (11, ubuntu-latest)](https://github.com/NganWave/seatunnel/actions/runs/40453802024/job/122023119087) `failure`; [Run / all-connectors-i t-2 (17, ubuntu-latest)](https://github.com/NganWave/seatunnel/actions/runs/40453802024/job/122023119101) `failure`; plus 33 other failed/cancelled jobs in the linked run. Observed log evidence: `MongodbCDCIT.testMongodbCdcMultiTableToMysqlE2e:331->assertionsSourceAndSink:726 ยป ConditionTimeout` `Failed to execute goal org.apache.maven.plugins:maven-failsafe-plugin:2.22.2:verify (default) on project connector-cdc-mongodb-e2e: There are test failures.` Please inspect or rerun only the named failed job where a rerun is appropriate. The logs establish the failing stage, but do not alone establish whether the current PR caused it. No matching upstream cure has been proved by this follow-up; a base sync alone is not a verified resolution, so no unrelated module/dependency patch is requested. My [previous source conclusion](https://github.com/apache/seatunnel/pull/12810#pullrequestreview-5667072425) remains unchanged, including its independent source/documentation requests. CI is not being passed by inference, and this follow-up is not an effective approval. Comparison recorded in this scan: base `dev`, `diverged`, ahead 41 / behind 59, no merge conflict. Branch drift is metadata here and is not an additional sync request. -- 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]
