Demanding builds can starve the runner process and kill the job

[jaimergp]

This is a known issue, which presents with the following symptoms:

• The job logs UI is irresponsive. They can be missing or reporting "In progress" when indeed they failed a while ago.

• The raw logs only show the first few lines:

2024-02-28T04:21:10.5308211Z Requested labels: cirun-openstack-cpu-large--8075232475-linux_aarch64_, linux, x64, self-hosted
2024-02-28T04:21:10.5308629Z Job defined at: conda-forge/mongodb-feedstock/.github/workflows/conda-build.yml@refs/pull/80/merge
2024-02-28T04:21:10.5308806Z Waiting for a runner to pick up this job...
2024-02-28T04:22:29.1192514Z Job is about to start running on the runner: cirun-conda-forge--mongodb-feedstock-fd6a0cc (repository)

• The jobs Summary UI shows the following annotation / error:

The self-hosted runner: cirun-conda-forge--mongodb-feedstock-fd6a0cc 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.

---

The solution is to either reduce resource usage or, if there are no other options, upgrade to a larger runner.