Skip to content
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

[build-and-test-arm] Self-hosted runner lost communication with server #34000

Open
crobert-1 opened this issue Jul 9, 2024 · 2 comments
Open
Assignees
Labels
arm64 Issues related to arm64 architecture ci-cd CI, CD, testing, build issues Stale

Comments

@crobert-1
Copy link
Member

crobert-1 commented Jul 9, 2024

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:

The self-hosted runner: 04922ab0a5cde170c99dee4153a188a070226aa0 lost communication with the server. Verify the machine is running and has a healthy network connection. Anything in your workflow that terminates the runner process, starves it for CPU/Memory, or blocks its network access can cause this error.

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

@crobert-1 crobert-1 added needs triage New item requiring triage arm64 Issues related to arm64 architecture ci-cd CI, CD, testing, build issues labels Jul 9, 2024
Copy link
Contributor

github-actions bot commented Sep 9, 2024

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 @open-telemetry/collector-contrib-triagers. If this issue is still relevant, please ping the code owners or leave a comment explaining why it is still relevant. Otherwise, please close it.

Copy link
Contributor

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 @open-telemetry/collector-contrib-triagers. If this issue is still relevant, please ping the code owners or leave a comment explaining why it is still relevant. Otherwise, please close it.

@github-actions github-actions bot added the Stale label Dec 11, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
arm64 Issues related to arm64 architecture ci-cd CI, CD, testing, build issues Stale
Projects
None yet
Development

No branches or pull requests

2 participants