Skip to content

no-response

no-response #14079

Triggered via schedule January 9, 2025 06:10
Status Failure
Total duration 49m 57s
Artifacts
This run and associated checks have been archived and are scheduled for deletion. Learn more about checks retention

no-response.yml

on: schedule
no-response
0s
no-response
Fit to window
Zoom out
Zoom in

Annotations

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