DanielLeens commented on PR #12907: URL: https://github.com/apache/seatunnel/pull/12907#issuecomment-6337986965
A CI-status correction on unchanged head `90c32948c0bcd99c40660d32942206da31fdfa1f`: my previous note described a queued/pending Build. The current [Build](https://github.com/apache/seatunnel/runs/118649659844) is now **failure**, so the old pending guidance is obsolete. Failed job families: `Run / Dead links`, `Run / unit-test`, `Run / edge-agent-it`. 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/1328837476-hug/seatunnel/actions/runs/39404189742/job/118565990538): the InterSystems IRIS driver URL ending in `JDK18/intersystems-jdbc-3.8.4.jar` returns HTTP 404. - [Run / unit-test (11, ubuntu-latest)](https://github.com/1328837476-hug/seatunnel/actions/runs/39404189742/job/118569175682): `JdbcOptionRuleCompletenessTest.testSinkRuleDeclaresAllSinkOptions` fails on unknown sink-fixture key `numeric_special_value_as_null`. - [Run / edge-agent-it (11, ubuntu-latest)](https://github.com/1328837476-hug/seatunnel/actions/runs/39404189742/job/118569176888): `JdbcOptionRuleCompletenessTest.testSinkRuleDeclaresAllSinkOptions` fails on unknown sink-fixture key `numeric_special_value_as_null`. Upstream/next-step check: The JDBC completeness-fixture failure is tracked in #12874; fix #12875 remains open and the mismatch is still in latest `dev`. Syncing current `dev` alone will not clear it. Once #12875 lands, sync and rerun the affected failed jobs rather than adding the unrelated option-fixture change here. 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 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 3, behind 18, 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]
