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

   The CI fact cited in my latest review has changed: the in-progress Build has 
now failed. The real blocking job is unit-test (17, ubuntu-latest), run 
40828465494/job 123297627304: PhysicalVertexTest setup reports Node failed to 
start with port-binding failures in the log; all-connectors-it-3 (11) is 
cancelled. My Spark decimal source clearance remains unchanged. Latest dev adds 
tests in PhysicalVertexTest but leaves the shared server startup fixture 
unchanged; candidate port fixes #13028/#13030 are still open. No merged fix for 
this startup failure is established, so a simple sync alone is not a verified 
cure. Rerun the failed/cancelled jobs first; do not add unrelated engine edits 
to this decimal PR.
   
   Checked 2026-10-29T17:13:10+00:00; head 
`1ce4e26cdbdcac4cf2d901c807463fe82cdf2822`. [Signal pull request 
update](https://github.com/apache/seatunnel/actions/runs/40828472287/job/123330615596)
 = `SUCCESS`; [Build](https://github.com/apache/seatunnel/runs/123363531370) = 
`FAILURE`
   
   Comparison: base `dev`, head `1ce4e26cdbdcac4cf2d901c807463fe82cdf2822`, 
`diverged`, ahead 3 / behind 5; GitHub mergeable state `blocked`. 
Behind/diverged alone is recorded metadata and does not add a sync request.
   
   Daniel has READ repository permission. This is a discussion/CI 
clarification, not a new complete source review, an effective APPROVED event or 
dismissal of historical requested changes. A write-capable maintainer must 
perform any required final approval/dismissal. Thanks for keeping the follow-up 
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]

Reply via email to