Skip to content
Run profiling

Run profiling #1676

Sign in to view logs

Run profiling

Run profiling #1676

Triggered via schedule February 8, 2025 00:20
@willGraham01willGraham01
⁠ 3599cdc
master
Status Failure
Total duration 3h 13m 49s
Artifacts –

run-profiling.yaml

on: schedule
Create unique output file identifier and artifact name
3s
Create unique output file identifier and artifact name
Scheduled / dispatch triggered profiling
3h 12m
Scheduled / dispatch triggered profiling
Comment triggered profiling  /  run_test_on_keyword_and_reply_with_result
Comment triggered profiling / run_test_on_keyword_and_reply_with_result
Upload profiling results
0s
Upload profiling results
Fit to window
Zoom out
Zoom in

Annotations

1 error
Scheduled / dispatch triggered profiling
The self-hosted runner: runner-deployment-b6nbg-r4z2s 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.