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

The hosted runner: GitHub Actions 13 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.

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

The hosted runner: GitHub Actions 48 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.

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

The hosted runner: GitHub Actions 24 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.

The process '/usr/bin/kitchen' failed with exit code 20

The process '/usr/bin/kitchen' failed with exit code 20

The process '/usr/bin/kitchen' failed with exit code 20

The process '/usr/bin/kitchen' failed with exit code 20

The process '/usr/bin/kitchen' failed with exit code 20