88fantasy commented on PR #12208:
URL: https://github.com/apache/seatunnel/pull/12208#issuecomment-6406011630

   Thanks @DanielLeens for checking the CI failures and identifying the 
upstream fix.
   
   I merged `dev@7604a83ec` and pushed the updated head `12ed6a859`. This 
includes #12938 (`cc54bb433`), which restores the UID required by the archived 
LLM wrapper fixture. The merge leaves the lineage modules, related API 
option/rule sources, and English/Chinese lineage documentation unchanged.
   
   Local validation on the new head, using JDK 11:
   
   - `./mvnw spotless:apply` — passed, with no tracked formatting changes.
   - Full-reactor `./mvnw -q -DskipTests verify` — passed.
   - Both lineage modules — 47 tests passed.
   - API option registration, option synchronization, and Markdown checks — 7 
tests passed.
   - `LLMBooleanOutputTest#readsLegacyFactoryWrapperWithValidationDisabled` — 
passed.
   
   All 55 selected tests completed with zero failures, errors, or skips. The PR 
description now records these results.
   
   The new-head 
[Build](https://github.com/88fantasy/seatunnel/actions/runs/40252464030) is 
still pending, with the Java 11/17 Linux/Windows unit-test lanes and 
transform-v2 part-2 lanes running or queued. The local fixture result does not 
establish CI success or compatibility with every historical wrapper.
   
   The separate Python container setup `Hash Sum mismatch` remains unverified 
on this head. If it recurs, I will retain the new job link for a separate 
fixture/mirror investigation, as suggested.
   
   Full unfiltered unit tests and real-cluster/E2E acceptance were not run 
locally. Engine submission-path token validation and its regression coverage 
remain in #12209 and #12210. Required Build completion and a write-capable 
maintainer’s final approval remain outstanding.
   


-- 
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]

Reply via email to