DanielLeens commented on PR #12898: URL: https://github.com/apache/seatunnel/pull/12898#issuecomment-6338001008
A CI-status correction on unchanged head `7ae92daee9750258baccf264b35b9e484ec2f74a`: my previous note described a queued/pending Build. The current [Build](https://github.com/apache/seatunnel/runs/118466264695) is now **failure**, so the old pending guidance is obsolete. Failed job families: `Run / engine-v2-it`, `Run / unit-test`, `Run / amazonSqs-connector-it`, `Run / connector-sensorsdata-it`. Concrete inspected log evidence (one representative JDK/OS per failed family; this does not claim every matrix leg has the identical cause): - [Run / engine-v2-it (11, ubuntu-latest)](https://github.com/nzw921rx/seatunnel/actions/runs/39373447057/job/118469935508): failed case(s): `testStopWithSavepointCompletesWhileSourceEmitsLargeSplit`. - [Run / unit-test (11, ubuntu-latest)](https://github.com/nzw921rx/seatunnel/actions/runs/39373447057/job/118469935763): `JdbcOptionRuleCompletenessTest.testSinkRuleDeclaresAllSinkOptions` fails on unknown sink-fixture key `numeric_special_value_as_null`. - [Run / amazonSqs-connector-it (11, ubuntu-latest)](https://github.com/nzw921rx/seatunnel/actions/runs/39373447057/job/118469936169): Maven wrapper bootstrap fails before the connector tests (`MavenWrapperMain` is missing). - [Run / connector-sensorsdata-it (17, ubuntu-latest)](https://github.com/nzw921rx/seatunnel/actions/runs/39373447057/job/118469936378): Maven wrapper bootstrap fails before the connector tests (`MavenWrapperMain` is missing). 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 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 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 4, 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]
