Skip to content

No Response

No Response #1111

Triggered via schedule January 9, 2025 05:33
Status Failure
Total duration 46m 2s
Artifacts

no-response.yml

on: schedule
noResponse
0s
noResponse
Fit to window
Zoom out
Zoom in

Annotations

1 error and 1 warning
noResponse
The hosted runner: GitHub Actions 330 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.
noResponse
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636