DanielLeens commented on PR #11932: URL: https://github.com/apache/seatunnel/pull/11932#issuecomment-6473895523
Thanks for the contribution. The merge-gate fact cited in my previous conclusion has changed: GitHub now reports a real merge conflict. This follow-up corrects that gate on the unchanged reviewed head; it is not another full source review or a sync request based only on being behind. Gate snapshot (2026-10-28T15:57:47+00:00), head `61eb51c29a5647288958da95e07ffdd34009c157`: [Build](https://github.com/apache/seatunnel/runs/121561538116) is `FAILURE`. The blocking jobs are [Run / amazonSqs-connector-it (17, ubuntu-latest)](https://github.com/apache/seatunnel/actions/runs/40308485470/job/121559126220) `failure`; [Build](https://github.com/apache/seatunnel/runs/121561538116) `failure`; [Run / amazonSqs-connector-it (17, ubuntu-latest)](https://github.com/apache/seatunnel/actions/runs/40308485470/job/121559126220) `failure`; [Build](https://github.com/apache/seatunnel/runs/121561538116) `failure`. Observed log evidence: `Failed to execute goal org.apache.maven.plugins:maven-failsafe-plugin:2.22.2:verify (default) on project connector-amazonsqs-e2e: There are test failures.` Please inspect or rerun only the named failed job where a rerun is appropriate. The logs establish the failing stage, but do not alone establish whether the current PR caused it. No matching upstream cure has been proved by this follow-up; a base sync alone is not a verified resolution, so no unrelated module/dependency patch is requested. My [previous source conclusion](https://github.com/apache/seatunnel/pull/11932#pullrequestreview-5651250431) remains clear for the reviewed scope. CI is not being passed by inference, and this follow-up is not an effective approval. Separately, GitHub reports merge conflicts with `dev`. Please sync the latest base and resolve the conflicts first; the resulting new head needs checks and re-review. This conflict gate is independent of CI and existing source findings. -- 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]
