You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
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.
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: