How do know the real error for Github Action? #144309
Replies: 1 comment
-
💬 Your Product Feedback Has Been Submitted 🎉 Thank you for taking the time to share your insights with us! Your feedback is invaluable as we build a better GitHub experience for all our users. Here's what you can expect moving forward ⏩
Where to look to see what's shipping 👀
What you can do in the meantime 💻
As a member of the GitHub community, your participation is essential. While we can't promise that every suggestion will be implemented, we want to emphasize that your feedback is instrumental in guiding our decisions and priorities. Thank you once again for your contribution to making GitHub even better! We're grateful for your ongoing support and collaboration in shaping the future of our platform. ⭐ |
Beta Was this translation helpful? Give feedback.
-
Select Topic Area
Bug
Body
We have recently ran into instability of our Github Action for our deploy pipeline. We have seen many different types of errors, but the jobs have started to trend longer, and then fail for all different reasons (some listed below). How can I diagnose the issue here? My inkling is that it is a memory problem, but there is no way to know currently it seems. Any help is appreciated!
ERROR: failed to solve: DeadlineExceeded: no active session for 2t223axyieb3dzf59xo8im026: context deadline exceeded
ERROR: failed to solve: Canceled: context canceled
The hosted runner encountered an error while running your job. (Error Type: Disconnect)
#9 ERROR: rpc error: code = Canceled desc = grpc: the client connection is closing ------ > exporting to client directory: ------ ERROR: failed to solve: Canceled: rpc error: code = Canceled desc = grpc: the client connection is closing
The runner has received a shutdown signal. This can happen when the runner service is stopped, or a manually started runner is canceled.
Received request to deprovision: The request was cancelled by the remote provider.
Beta Was this translation helpful? Give feedback.
All reactions