Labeled switch documentation #16621
Triggered via pull request
September 11, 2024 09:19
LiterallyVoid
Status
Failure
Total duration
3h 30m 12s
Artifacts
–
ci.yaml
on: pull_request
x86_64-linux-debug
3h 7m
x86_64-linux-release
1h 33m
aarch64-linux-debug
3h 29m
aarch64-linux-release
2h 22m
x86_64-macos-release
1h 16m
aarch64-macos-debug
34m 39s
aarch64-macos-release
32m 49s
x86_64-windows-debug
27m 41s
x86_64-windows-release
27m 41s
aarch64-windows
1h 0m
Annotations
4 errors
|
x86_64-windows-release
The runner has received a shutdown signal. This can happen when the runner service is stopped, or a manually started runner is canceled.
|
|
x86_64-windows-release
The self-hosted runner: George 1 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.
|
|
x86_64-windows-debug
The runner has received a shutdown signal. This can happen when the runner service is stopped, or a manually started runner is canceled.
|
|
x86_64-windows-debug
The self-hosted runner: George 5 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.
|