DanielLeens commented on PR #12284:
URL: https://github.com/apache/seatunnel/pull/12284#issuecomment-5716973918

   CI result for the current head `672bd40ed8a` (fork run 35096464194, 
completed 2026-09-17): every leg that exercises this PR passed, and the merge 
with `dev` cleared the MinIO image failures (Iceberg S3, S3 file and Databend 
now pass).
   
   - `unit-test` passed on all four matrix entries.
   - `mysql-cdc-connector-it` passed on both JDKs, which covers both SQL 
transform E2E flows with their savepoint and restore cycles.
   - `transform-v2-it-part-2` passed on both JDKs and `transform-v2-it-part-1` 
passed on JDK 8.
   
   The six failed legs fail on `dev` as well (latest completed `dev` Build, 
`c7304ace6e1`, 2026-09-17, is red on the same legs), and each already has an 
owning PR:
   
   | Leg | Failing test | Owner |
   |---|---|---|
   | transform-v2-it-part-1 (JDK 11) | 
`TestFilterRowKindIT.testFilterRowKindMultiTable` on a Flink container, Assert 
row counts across restarts | #12216, #12350 |
   | all-connectors-it-2 (both) | `OpengaussCDCIT.testAddFieldWithRestore` | 
#12350 |
   | all-connectors-it-7 (JDK 11) | 
`PostgresCDCIT.testPostgresCdcSnapshotOnlyAndCommittedOffsetStartupModes` | 
#12261 |
   | engine-v2-it (JDK 11) | `BackpressureSlowSinkIT` | #12313, #12350 |
   | engine-v2-it (JDK 11) | `SplitClusterFaultToleranceIT` cancel test, 
expected CANCELED but was FAILED | #12311 |
   | rocketmq-connector-it (JDK 11) | `RocketMqIT` | #12115, #12375, #12350 |
   
   `jdbc-connectors-it-part-1` (JDK 8), `paimon-connector-it` (both) and 
`kudu-connector-it` (JDK 11) were cancelled by the job time limit; the first 
two are cancelled on the `dev` Build too.
   
   No change to this PR follows from these results. Once the owning PRs land on 
`dev` I will merge `dev` again and let the Build rerun.


-- 
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]

Reply via email to