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

   Rechecked the current CI gate after my previous source-clear review.
   
   The source-side conclusion from my last review is unchanged: I still do not 
see a reopened Daniel-side blocker in the E2E stability diff. The CI fact has 
changed, though: the previous pending/queued Build has now completed as failed.
   
   Current gate details:
   ```text
   Apache aggregate check
     -> Build: failure
     -> https://github.com/apache/seatunnel/runs/86548891589
         -> fork workflow run: davidzollo/seatunnel/actions/runs/29154336109
             -> failed job: Run / kafka-connector-it (8, ubuntu-latest)
             -> cancelled job after failure: Run / kafka-connector-it (11, 
ubuntu-latest)
   ```
   
   I tried to fetch the failed job log, but GitHub returned a transient log 
stream cancellation while downloading it. Since this PR directly touches E2E 
stability and the failed lane is Kafka-related, I would not treat this as a 
generic “sync only” issue yet. The lowest-cost next step is to rerun or inspect 
the failed `kafka-connector-it (8, ubuntu-latest)` job first. If the rerun 
fails the same way, please paste that failing job link/log snippet here and I 
can help narrow it down against the current head.
   
   ### Merge conclusion: source clear, waiting for CI
   Blocking items: none from Daniel's current source review.
   Current merge gate: failed Kafka connector integration-test lane above.
   


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