-
-
Notifications
You must be signed in to change notification settings - Fork 180
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
PR Status check hangs on "Pending" #280
Comments
Pending
Hey! Is the PR public, can you give me the link? |
Hey, I'm afraid not it's on a private repo. Is there any other info I can provide? |
There must be some place where if failed in the CI logs. It sets the pending status first and then updates it when the checks are completed. |
I don't recall seeing any error logs on CI - I'll make sure and take a closer look at the output next time it happens. |
@siddharthkp It has just happened again for us and there are 100% no error logs from the |
It's difficult to say what's up without debugging 😢 Can you add me as a temporary collaborator ? |
+1 same here, deploys do not work because status is pending. Solved by updating github token |
Same here, running on CircleCI. Seems to happens seldom and randomly. The job passes successfully without errors (https://imgur.com/a/Gzc4iOo), so I'm guessing the problem is on the service side. |
Note that it seems like GitHub was partially down yesterday & today (I've been having error 500s here and there), so that is likely related |
I've been experiencing this intermittently for over a month |
Hi 👋 There are multiple reasons why this can happen, definitely needs some work. Make sure you add your 👍 to the theme on v1 roadmap: #306 (comment) |
Do you want to request a feature or report a bug?
Bug
What is the current behavior?
Pull request status reporting occasionally gets stuck in the
Pending
statusIf the current behavior is a bug, please provide the steps to reproduce.
What is the expected behavior?
The bundlesize status should be reported after calculating
Please mention other relevant information.
The text was updated successfully, but these errors were encountered: