Phoenix500526 commented on issue #23400: URL: https://github.com/apache/datafusion/issues/23400#issuecomment-4936280944
I investigated the merge-group run for #23324. The merge queue did not remove the PR after a successful CI run. It removed it after [attempt 1 of the Rust workflow](https://github.com/apache/datafusion/actions/runs/28968722623/attempts/1) failed on merge-group commit [301e684](https://github.com/apache/datafusion/commit/301e684b583fb2d3661f73c6489f81891f1150aa). At 19:16:38 UTC, four required jobs were marked as failed: * cargo test doc (amd64) * cargo check datafusion-substrait features * verify benchmark results (amd64) * Run sqllogictest in Substrait round-trip mode Their logs show that the RunsOn runners received shutdown signals. GitHub removed the PR from the merge queue at 19:17:05. The RunsOn bot started [attempt 2](https://github.com/apache/datafusion/actions/runs/28968722623/attempts/2) at 19:22:40, after the PR had already been removed. That retry passed, and GitHub now displays the latest attempt, which is why the checks currently appear green. The affected runners were Spot instances, so this was likely a transient runner interruption, although RunsOn or CloudWatch logs would be needed to confirm the underlying infrastructure event. Therefore, the merge queue did not reject a successful run. It reacted to the failed first attempt, while the UI now shows the successful retry. Re-adding the PR created a new merge-group run, which passed and merged successfully. -- 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] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
