-
Notifications
You must be signed in to change notification settings - Fork 2.6k
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
Automation misbehaving due to Github October 21 incident #9881
Comments
Update: looks like we are slowly starting to receive webhooks for past events and things are starting to move. |
Update: old webhooks have caught up, new webhooks are working are normally. |
Looking good to me. I can't tell that anything merged that shouldn't have, but I haven't looked beyond the spot checks linked here. |
Everything (related to this outage at least) is looking fine. |
@amwat: Closing this issue. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
Opening this as an issue to refer to if/when you find weird behavior over the next day or two. GitHub is mitigating an incident.
At a minimum, I guarantee prow isn't doing things right now because:
We may have some mitigation of our own to do, since it's unclear whether github will release/replay webhooks, or we'll need to do some sort of reconciliation on our own.
Timeline
/kind bug
/priority critical-urgent
/assign @amwat
as go.k8s.io/oncall lists him as the test-infra oncall
The text was updated successfully, but these errors were encountered: