DanielLeens commented on PR #12807: URL: https://github.com/apache/seatunnel/pull/12807#issuecomment-6338038958
A CI-status correction on unchanged head `3c333b52ee05a91974f4166454c8ef66abf5e193`: my previous note described a queued/pending Build. The current [Build](https://github.com/apache/seatunnel/runs/119069753180) is now **failure**, so the old pending guidance is obsolete. Failed job families: `Run / unit-test`, `Run / jdbc-connectors-it-part-4`. Concrete inspected log evidence (one representative JDK/OS per failed family; this does not claim every matrix leg has the identical cause): - [Run / unit-test (11, ubuntu-latest)](https://github.com/ricky2129/seatunnel/actions/runs/39551627031/job/119062786700): `LLMBooleanOutputTest.readsLegacyFactoryWrapperWithValidationDisabled` fails with `InvalidClassException` on `AbstractMultiCatalogTransform`. - [Run / jdbc-connectors-it-part-4 (17, ubuntu-latest)](https://github.com/ricky2129/seatunnel/actions/runs/39551627031/job/119062787597): Maven wrapper bootstrap fails before the connector tests (`MavenWrapperMain` is missing). Upstream/next-step check: The archived LLM fixture is tracked in #12929; proposed fix #12938 remains open. Latest `dev` (`99ea16b9d6bdce452d4c4955581ccc7236a81bbd`) still has no explicit historical UID on `AbstractMultiCatalogTransform`. Syncing today will not fix that observed failure. Once the fix lands in `dev`, sync and rerun the affected failed jobs. Keep unrelated transform-serialization changes out of this PR. The missing Maven wrapper class is a bootstrap failure, not an executed connector assertion. No matching base-branch wrapper correction was identified. A targeted retry of that failed job after download/bootstrap availability recovers is the useful diagnostic; do not add product dependencies to compensate. 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 6, behind 9, 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]
