SEZ9 commented on PR #12454:
URL: https://github.com/apache/seatunnel/pull/12454#issuecomment-5852309280

   @DanielLeens A new CI result makes the remaining dependency explicit. On 
current head `addd4a621854`, [all-connectors-it-5 / Java 
11](https://github.com/SEZ9/seatunnel/actions/runs/36285303193/job/108537497579)
 failed `OceanBaseCDCCompatibilityIT` at 03:27:04 UTC on September 27: 5 tests, 
0 failures, 4 errors, 0 skips. All four errors end in 
`NotSerializableException: io.debezium.relational.TableId`, the same duplicate 
packaged Debezium runtime failure seen on #12298/#12299.
   
   The independent packaging fix in #12489 has now passed all 5 OceanBase 
compatibility cases on each JVM: [Java 
8](https://github.com/SEZ9/seatunnel/actions/runs/36284739243/job/108524753565) 
/ [Java 
11](https://github.com/SEZ9/seatunnel/actions/runs/36284739243/job/108524753606).
 Both complete shards are also successful, including 30 Fluss tests per JVM, 
with no added skips. The OceanBase cases retain the existing 
snapshot/incremental assertions and add actual packaged-jar serialization 
checks in both jar orders.
   
   I am keeping that connector fix separate from this PR's recovery/WAL 
changes. Once #12489 is merged, I can update this branch and the feature 
branches to consume it; local merge preflight against current dev found no 
textual conflicts. This PR's other jobs are still running. #12489's full Build 
is not green yet either: its first attempt has the PayPal retry-fixture and 
PostgreSQL restored-offset failures already reported above, with failed-job 
retries to be requested automatically when the workflow finishes. This comment 
records the concrete dependency and validation, not a claim that either full 
Build has passed.
   


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