-
Notifications
You must be signed in to change notification settings - Fork 1.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
General issue #18363
Comments
Hi @ashutosh7107, Lost communication generally indicates that the system was under very high load. From the information you shared it's not possible to tell what is going on. Could you either (a) share a link to a relevant job/repository on which this is happening, or (b) if the previous is not possible - which means you're a paying customer - create a support ticket . |
One question based on the workflow file:
Are you sure communication is not lost because it's being cancelled by another workflow? |
Sharing a repo link won't be possible as per organization policy it's an internal repo. |
In that case, please create a support ticket. |
The above steps is used to cancel any previously running workflows for the same branch or pull request. |
I created a new discussion for the same under this link. Please check if that is fine. |
That is just as problematic as discussing it here, as it's a public page. Creating a support ticket is going to work best, as that allows information to be shared in private. How to create a support ticket is described here: https://docs.github.com/en/support/contacting-github-support/creating-a-support-ticket |
Oh Ok..!! Thanks for the guidance. I created a ticket https://support.github.com/ticket/personal/0/3154306, seems fine now |
I am using the below code ql workflow but everytime after 30-40 minutes of running it is giving me below error
The hosted runner: GitHub Actions 206 lost communication with the server. Anything in your workflow that terminates the runner process, starves it for CPU/Memory, or blocks its network access can cause this error.
FAILURE: Build failed with an exception.
Gradle build daemon disappeared unexpectedly (it may have been killed or may have crashed)
Any suggestions how to resolve the above error?
The text was updated successfully, but these errors were encountered: