SEZ9 commented on PR #11597:
URL: https://github.com/apache/seatunnel/pull/11597#issuecomment-6487512419

   Following up on the CI point only.
   
   @davidzollo, thanks for the update. The thread records that the previous 
Build was cancelled at workflow level after about 24 hours with most jobs still 
queued, so it did not show a product-code failure, and that a fresh Build was 
queued for `de507b8e2c7` (`de507b8e2c7814f2d2f5bba6256c1946e9562db9`, based on 
`1882a579236c451df59ae8782a53c4460fb926f1`).
   
   I can't verify the current state from here, so could you confirm:
   
   1. Whether the re-queued Build ran to completion this time and what its 
outcome was.
   2. If it finished with failures, whether they look related to the slot-usage 
changes or are infrastructure/flaky, so we know whether a re-run is the right 
call.
   3. The exact head the Build ran against, in case anything has been pushed 
since `de507b8e2c7`.
   
   Once that is confirmed, I'll do the final pass on this point. No new asks 
beyond the CI follow-up.
   
   <!-- streview-comment:2122 -->


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