You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@seatunnel.apache.org by "DanielLeens (via GitHub)" <gi...@apache.org> on 2026/08/06 04:38:28 UTC

Re: [PR] [Fix][CI] Fix upgrade compatibility workflow setup [seatunnel]

DanielLeens commented on PR #11611:
URL: https://github.com/apache/seatunnel/pull/11611#issuecomment-5200446803

   Follow-up on the `Build` gate I flagged as still queued in my last review: it has now completed and failed on the same head (`abb2baa18d`).
   
   I checked the failing lanes: `paimon-connector-it (8, ubuntu-latest)` fails in `connector-paimon-e2e`, and `kafka-connector-it (11, ubuntu-latest)` also fails. Both are E2E suites for connectors this PR does not touch at all — this PR only changes `.github/workflows/upgrade_compatibility.yml` and files under `tools/upgrade_compatibility/`. This matches the pattern from the last two Build failures on earlier heads of this same PR (an unrelated Testcontainers pull timeout, then an unrelated Iceberg CDC E2E assertion) — none of them have been in the upgrade-compatibility path this PR actually changed.
   
   This branch is also currently behind `dev` (diverged, `behind_by=2`, `ahead_by=6`), so the lowest-cost next step is to sync onto the latest `dev` and rerun `Build` rather than debugging Paimon/Kafka E2E flakiness on a stale base. From Daniel's side there is no outstanding source-level blocker on this head.
   
   If it still fails on the synced head, please share the failing job link and I'll take another look.


-- 
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: commits-unsubscribe@seatunnel.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org