SEPURI-SAI-KRISHNA commented on PR #12568: URL: https://github.com/apache/seatunnel/pull/12568#issuecomment-5965791817
Rerun done. Both legs I asked about passed, so the `PaimonSinkCDCIT` failure was flaky, as hoped. Run `36966371906` attempt 2, no new commit, head still `314556b79`: | leg | attempt 1 | attempt 2 | | --- | --- | --- | | `all-connectors-it-7 (11)` | `PostgresCDCIT`, 1 error | **success**, completed 19:57:42Z | | `paimon-connector-it (11)` | `PaimonSinkCDCIT.testChangelogLookup`, 1 failure | **success**, completed 18:48:23Z | Job totals for the attempt: 82 successful, 11 skipped, 1 cancelled, **0 failed**. Since `PaimonSinkCDCIT` did not recur, I am not opening an issue for it. One observation with no second occurrence is not worth filing, which is what I said I would do either way. One thing that still needs a word, because the badge on this PR is red and it is not a test. The only non-success in the attempt is `Build website`, cancelled at 19:30:08Z, and the aggregating `Build` check-run then ended `timed_out` at 20:14:48Z. Both numbered test legs had already finished green before that. So the red badge is a harness timeout plus a cancelled website build, not a failing test. @nzw921rx would you like another rerun to get a clean badge, or is the job-level result above enough given the diff is one file in `seatunnel-api` and the `MultiTableSinkWriterTest` additions were green on all four unit-test legs? Happy to trigger another if you prefer the check itself green before merging. -- 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]
