DanielLeens commented on PR #11301:
URL: https://github.com/apache/seatunnel/pull/11301#issuecomment-4950909843
Rechecked the current CI gate after my previous source-clear review.
The source-side conclusion from my last review is unchanged: I still do not
see a reopened Daniel-side blocker in the upgrade-compatibility workflow diff.
The CI fact has changed, though: the previous in-progress `Build` has now
completed as failed.
Current gate details:
```text
Apache aggregate check
-> Build: failure
-> https://github.com/apache/seatunnel/runs/86271094088
-> fork workflow run: goutamadwant/seatunnel/actions/runs/29063812030
-> failed job: Run / Dead links
-> failed job: Run / all-connectors-it-3 (11, ubuntu-latest)
-> failed job: Run / kafka-connector-it (8, ubuntu-latest)
-> cancelled sibling job: Run / all-connectors-it-3 (8,
ubuntu-latest)
```
These red lanes do not line up with the PR-owned upgrade-compatibility
workflow path itself, and this branch is now behind the latest `dev` by 5
commits (`compare status: diverged`, `ahead_by=9`, `behind_by=5`). I also
checked the current `dev` head, but its aggregate Build is still pending right
now, so I cannot point to a confirmed upstream fix yet. The lowest-cost next
step is to sync with the latest `dev` and rerun `Build` first. If the same
lanes still fail on the synced head, please drop the rerun links here and I can
help narrow down whether any of them are genuinely tied to this PR.
### Merge conclusion: source clear, waiting for CI
Blocking items: none from Daniel's current source review.
Current merge gate: failed unrelated CI lanes above; please sync latest
`dev` and rerun first.
--
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]
