DanielLeens commented on PR #10521: URL: https://github.com/apache/seatunnel/pull/10521#issuecomment-6338120666
A CI-status correction on unchanged head `7b53f00f970803b9b301c4a2749c92046b4d0451`: my previous note described a queued/pending Build. The current [Build](https://github.com/apache/seatunnel/runs/118601168813) is now **failure**, so the old pending guidance is obsolete. Failed job families: `Run / Dead links`, `Run / edge-agent-it`, `Run / unit-test`. Concrete inspected log evidence (one representative JDK/OS per failed family; this does not claim every matrix leg has the identical cause): - [Run / Dead links](https://github.com/852511489/seatunnel/actions/runs/39397626173/job/118544172220): the InterSystems IRIS driver URL ending in `JDK18/intersystems-jdbc-3.8.4.jar` returns HTTP 404. - [Run / edge-agent-it (11, ubuntu-latest)](https://github.com/852511489/seatunnel/actions/runs/39397626173/job/118547203855): `LLMBooleanOutputTest.readsLegacyFactoryWrapperWithValidationDisabled` fails with `InvalidClassException` on `AbstractMultiCatalogTransform`. - [Run / unit-test (11, ubuntu-latest)](https://github.com/852511489/seatunnel/actions/runs/39397626173/job/118547203950): `LLMBooleanOutputTest.readsLegacyFactoryWrapperWithValidationDisabled` fails with `InvalidClassException` on `AbstractMultiCatalogTransform`. 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 same IRIS driver link is still in the latest `dev` JDBC docs (EN source line 354, ZH source line 350); no base-branch correction was found. A simple sync or blind rerun is not a demonstrated fix for a persistent 404. This shared documentation link should be corrected in its own focused change, then incorporated into affected branches; it is not a reason to change this connector's runtime dependencies. My earlier source/test/documentation blockers remain in force; these CI facts do not clear them. Please follow the existing numbered findings before requesting a new full review. The branch is ahead 15, behind 10, 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]
