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

   Thanks for the +1, @dybyte!
   
   Quick status note since your approval was conditional on CI: as of right 
now, the `Build` check on the current head 
`2b840e97663480e10bef169ac963a0ae6580dccb` is still `failure` 
(https://github.com/apache/seatunnel/runs/96156779577). No new commit has 
landed since my two APPROVED reviews on this head, so nothing has changed on my 
side — this is just a live-status update.
   
   I'm not re-deriving the failing jobs from scratch in this note; my 
permission on this repository is read-only, so I can't trigger a rerun myself. 
The concrete next step is for @agarwalrahul2702 to rerun the failed jobs on the 
fork's `Build` run and confirm it goes green.
   
   One more thing worth flagging so nobody is confused by the review summary: 
`reviewDecision` on this PR is still showing `CHANGES_REQUESTED` overall, but 
that's aggregating the earlier-round CHANGES_REQUESTED states from @nzw921rx, 
@davidzollo, and an early round from @SEZ9 that haven't been re-submitted as 
approvals against this head — it's not a new blocker from any of them on the 
current diff as far as I can tell. My own APPROVED conclusion isn't conditional 
on anything further from the source side.
   


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