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

The runner has received a shutdown signal. This can happen when the runner service is stopped, or a manually started runner is canceled. #3724

Open
HarshadDGhorpade-eaton opened this issue Feb 24, 2025 · 0 comments
Labels
bug Something isn't working

Comments

@HarshadDGhorpade-eaton
Copy link

Describe the bug
Time to time we're getting this error and workflow is getting canceled due to that, its very frustating. We have looked into couple of other issues as well:
The runner has received a shutdown signal. · Issue #6709 · actions/runner-images

The runner has received a shutdown signal. · actions/runner-images · Discussion #7188

we have reduced number of threads needed for our build to 28 from total capacity of 32 but still its same.

Runner Version and Platform

Runner version : '2.322.0'
We're using larger runner with 32 cores
Image: ubuntu-22.04
Version: 20250209.1.0

OS of the machine running the runner? OSX/Windows/Linux/...
OS : Ubuntu 22.04.5

What's not working?

The runner has received a shutdown signal. This can happen when the runner service is stopped, or a manually started runner is canceled.
Process completed with exit code 137.
The operation was canceled.
@HarshadDGhorpade-eaton HarshadDGhorpade-eaton added the bug Something isn't working label Feb 24, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant