Rangsh commented on PR #12218: URL: https://github.com/apache/seatunnel/pull/12218#issuecomment-5652095993
@SEZ9 @DanielLeens Re-ran the failed/cancelled jobs on the same head (`fee6db3b3c`) via `--failed` on [Rangsh/seatunnel run 34558932185](https://github.com/Rangsh/seatunnel/actions/runs/34558932185). Results: | Job | Before | After `--failed` rerun | Notes | |---|---|---|---| | `transform-v2-it-part-1 (11)` | failure | **success** | Confirmed flake — previous failure was `TestFilterRowKindIT.testFilterRowKindMultiTable`; green on rerun | | `all-connectors-it-2 (8)` | failure | failure again | Unrelated infra — see below | | `paimon-connector-it (11)` | cancelled | failure | Unrelated infra — see below | **Remaining failures (same root cause, unrelated to this PR):** 1. [`all-connectors-it-2 (8)`](https://github.com/Rangsh/seatunnel/actions/runs/34558932185/job/103669088264) — `IcebergSourceIT.startUp` `ContainerFetchException: Can't get Docker image: minio/minio:RELEASE.2024-06-13T22-53-53Z` Cause: `Status 404: pull access denied for minio/minio ... requested access to the resource is denied` 2. [`paimon-connector-it (11)`](https://github.com/Rangsh/seatunnel/actions/runs/34558932185/job/103669088312) — `PaimonWithS3IT.startUp` Same `minio/minio` Docker Hub pull denial at startup (before any Paimon/engine logic under test). Other Paimon ITs in the same job passed (`PaimonIT`, `PaimonSinkCDCIT`, `PaimonStreamReadIT`, etc.). Neither failure path touches `TaskExecutionService` / the post-publish rollback this PR changes. The transform job that previously failed is now green on the same commit, which further supports these as pre-existing / infra flakes rather than regressions from this diff. Overall on this head after the rerun: **77 success / 14 skipped / 2 failure** (both MinIO image-pull). Please take another look for merge when convenient. -- 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]
