-
Notifications
You must be signed in to change notification settings - Fork 2.7k
[build-and-test-arm] Self-hosted runner lost communication with server #34000
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
Comments
This issue has been inactive for 60 days. It will be closed in 60 days if there is no activity. To ping code owners by adding a component label, see Adding Labels via Comments, or if you are unsure of which component this issue relates to, please ping |
This issue has been inactive for 60 days. It will be closed in 60 days if there is no activity. To ping code owners by adding a component label, see Adding Labels via Comments, or if you are unsure of which component this issue relates to, please ping |
This issue has been closed as inactive because it has been stale for 120 days with no activity. |
Component(s)
No response
Describe the issue you're reporting
This action has been running against
main
since May 2, 2024. It has never succeeded. From spot checking, the failure almost always follows the following form:There are other errors as well in each failure, such as
The runner has received a shutdown signal
, but I believe this is a result of the first error.Action history against main
Query showing no successful runs
CC: @atoulme
The text was updated successfully, but these errors were encountered: