DanielLeens commented on PR #12850: URL: https://github.com/apache/seatunnel/pull/12850#issuecomment-6338025655
A CI-status correction on unchanged head `2709fec662478154ca74f1b3e67bfc332d2aa31f`: my previous note described a queued/pending Build. The current [Build](https://github.com/apache/seatunnel/runs/117466885504) is now **failure**, so the old pending guidance is obsolete. Failed job families: `Run / transform-v2-it-part-2`, `Run / all-connectors-it-6`, `Run / hbase-connector-it`, `Run / all-connectors-it-2`, `Run / mysql-cdc-connector-it`. Concrete inspected log evidence (one representative JDK/OS per failed family; this does not claim every matrix leg has the identical cause): - [Run / transform-v2-it-part-2 (11, ubuntu-latest)](https://github.com/goutamadwant/seatunnel/actions/runs/39047772093/job/117614115496): JUnit reports that no supporting `TestTemplateInvocationContextProvider` supplies an invocation. - [Run / hbase-connector-it (11, ubuntu-latest)](https://github.com/goutamadwant/seatunnel/actions/runs/39047772093/job/117614115677): JUnit reports that no supporting `TestTemplateInvocationContextProvider` supplies an invocation. - [Run / all-connectors-it-6 (11, ubuntu-latest)](https://github.com/goutamadwant/seatunnel/actions/runs/39047772093/job/117614115697): JUnit reports that no supporting `TestTemplateInvocationContextProvider` supplies an invocation. - [Run / mysql-cdc-connector-it (11, ubuntu-latest)](https://github.com/goutamadwant/seatunnel/actions/runs/39047772093/job/117614115739): JUnit reports that no supporting `TestTemplateInvocationContextProvider` supplies an invocation. - [Run / all-connectors-it-2 (11, ubuntu-latest)](https://github.com/goutamadwant/seatunnel/actions/runs/39047772093/job/117614115756): JUnit reports that no supporting `TestTemplateInvocationContextProvider` supplies an invocation. Upstream/next-step check: The template-provider symptom has a separate framework proposal, #12895, which remains open rather than merged into `dev`. I am not claiming it is a proven cure for every shard; it is the relevant shared-harness follow-up. Do not change connector behavior to work around a suite with no selected invocation. Recheck these failed lanes after the shared harness correction is available. My previous source-level conclusion remains unchanged: no outstanding source blocker from my side. This is a CI-status follow-up, not a fresh full code review or formal approval. The branch is ahead 1, behind 37, compare `diverged` against `dev`; this drift is recorded independently, not used as a generic sync request. A successful required Build and write-capable maintainer approval remain merge gates. Thanks for the contribution and for keeping the fix focused. -- 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]
