-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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
GitHub is not getting the result of the Travis #1457
Comments
It used to happen before but it seems to have increased the number of times we see this error. It usually gets solved with a simple close and re-open. Let's see if this is just a transient problem. |
Hi @Adirio, Many PR's are facing that and yes, I already tried close and re-open as re-tests. Another example is: #1449 Hi @mengqiy and @DirectXMan12, See that the suggested solution to solve it is to revoke the access and authorising it again. Let's try it? |
/kind bug |
we'd need a github admin for that, I think. Can't at-mention the github admins team here b/c it's defined in the kubernetes org. Let me figure out a person to ping. |
/assign |
Okay, there definitely was something funky going on. The webhooks were in place, but there was no app enabled for the repo (or authorized for the org itself...). I've re-authorized it for kubebuilder. Let me know if there continues to be a problem. 👍 |
Really tks @mrbobbytables. |
Problem
When we check the CI jobs. in the Travis, all finished successfully. However, we are unable to merge since the GB is showing that it still pending.
NOTE: It happens with a few PR's. We can use #1454 as an example.
The text was updated successfully, but these errors were encountered: