DanielLeens commented on PR #12919:
URL: https://github.com/apache/seatunnel/pull/12919#issuecomment-6337718849

   A CI-status follow-up on the unchanged head 
`17e4ddaf2e4918d245b00b31ebf60a22cacae7f6`: my earlier note described Build as 
pending/in progress. That fact is obsolete. [The current head's fork 
Build](https://github.com/fatmanverse/seatunnel/actions/runs/39393717869) has 
completed with **failure**. The four `unit-test` matrix legs are red; the JDK 
11 Ubuntu log I inspected fails at 
`LLMBooleanOutputTest.readsLegacyFactoryWrapperWithValidationDisabled` failing 
with `InvalidClassException` on `AbstractMultiCatalogTransform`. The 
`edge-agent-it` lanes are also red; the inspected JDK 11 Linux log stops at the 
same transform test.
   
   I checked the owning code on latest `dev` 
(`99ea16b9d6bdce452d4c4955581ccc7236a81bbd`) and the upstream tracking state: 
#12929 remains open, and its proposed fix #12938 is still open rather than 
present in the base. This is outside this PR's diff. **Syncing current `dev` 
alone will not fix that observed failure.** Please keep this PR focused; once 
#12938 lands in `dev`, sync the base and rerun the affected failed jobs for the 
resulting head. There is no need to add unrelated transform serialization 
changes here.
   
   My earlier source-level conclusion remains unchanged: no outstanding source 
blocker from my side. This is a CI follow-up, not a new full code review or 
formal approval. The branch is currently ahead 1, behind 10, compare 
`diverged`, with no merge conflict; the behind fact is recorded separately from 
the pending upstream fix. A green head-specific Build and write-capable 
maintainer approval are still required. Thanks for the contribution and 
patience with the shared CI failure.
   


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