-
Notifications
You must be signed in to change notification settings - Fork 27.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ci.yaml is not getting run on pull request, possible dropped messages from pubsub #121647
Comments
In each case whether it saw the checkRuns or did not the hash was the same: 465dd99d7c0f9ab49bca6fefc46146f3307e4296 |
This is also not the newest change but the one before it with failed runs. We should be looking to update the hash bff496f. In the picture below that is the newest hash. It looks like we did not pick up change request for this new hash. Looking to see if this was github failing to deliver a payload. |
We did get the webhook payload from github with the correct information:
With the correct sha:
|
It appears we just "lost" this or pub sub did not send it to us. Once I updated the branch the checks were immediately picked up and everything appeared as normal with all the checks getting kicked off. We never received the updated synchronized request for the issue above. |
Obsolete. Will revisit if this happens again. |
This thread has been automatically locked since there has not been any recent activity after it was closed. If you are still experiencing a similar issue, please open a new bug, including the output of |
ci.yaml is either not getting scheduled or in this case I believe not getting rescheduled.
flutter/engine#39915
For some reason earlier the check was getting scheduled. Tests were failing and several commits were sent to make fixes for those tests. It appears that the test was never rescheduled as there are logs saying that there are no checkRuns for this pr.
Here is the earlier run which shows that the ci.yaml validation test was in fact scheduled and did run to completion.
From an initial look at the code it appears that the checkRuns did not get scheduled.
The text was updated successfully, but these errors were encountered: