SEZ9 commented on PR #12489: URL: https://github.com/apache/seatunnel/pull/12489#issuecomment-5853619667
@DanielLeens The complete fork [Build run 36284739243](https://github.com/SEZ9/seatunnel/actions/runs/36284739243) has now succeeded on the reviewed commit `6709cfc118199013be66a4ef83409adb2f030c2d`: 43 successful jobs and 32 existing conditional skips, with no failed jobs. Attempt 2 reran only the two jobs that failed in attempt 1; the other 41 successful jobs were retained: - [PostgreSQL Java 11, job 108560866308](https://github.com/SEZ9/seatunnel/actions/runs/36284739243/job/108560866308): `PostgresCDCIT` passed all 37 tests with zero failures, errors or skips, and the whole job succeeded at 06:28:48 UTC on September 27. - [Windows Java 11 unit tests, job 108560866479](https://github.com/SEZ9/seatunnel/actions/runs/36284739243/job/108560866479): the complete Maven reactor reported `BUILD SUCCESS`, and the whole job succeeded at 06:55:21 UTC. `PayPalClientTest` passed all 23 tests; the PayPal module passed all 59 tests with zero failures, errors or skips. No source, workflow, timeout or test-skip changes were made between attempts. The OceanBase compatibility cases had already passed on both Java 8 and Java 11 in attempt 1, including the packaged-jar serialization checks and existing data assertions. This confirms that #12489 can pass independently of #12454. The two feature PRs #12298 and #12299 need this dependency fix in their base to remove their confirmed OceanBase serialization failures while keeping the dependency patch out of their feature diffs. The Apache PR's Build check is still awaiting the scheduled status synchronization at the time of this comment; the successful result above is the completed fork Build, not a manually changed check status. I am continuing to monitor that synchronization. -- 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]
