Update README.md #897
kringbuild.yml
on: push
Windows50
/
build
4m 27s
Windows51
/
build
16m 9s
Windows52
/
build
4m 22s
Quick Checks
7s
TestWindows50
/
test
TestWindows51
/
test
TestWindows52
/
test
TestPackage50
/
test
TestPackage51
/
test
TestPackage52
/
test
Annotations
16 errors
|
Windows52 / build
The runner has received a shutdown signal. This can happen when the runner service is stopped, or a manually started runner is canceled.
|
|
Windows52 / build
The operation was canceled.
|
|
Windows50 / build
The runner has received a shutdown signal. This can happen when the runner service is stopped, or a manually started runner is canceled.
|
|
Windows50 / build
The operation was canceled.
|
|
Android50
The runner has received a shutdown signal. This can happen when the runner service is stopped, or a manually started runner is canceled.
|
|
Android50
The self-hosted runner: i-083a595c2461e46fa 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.
|
|
Linux50
The runner has received a shutdown signal. This can happen when the runner service is stopped, or a manually started runner is canceled.
|
|
Linux50
The self-hosted runner: i-0cffedea1a67ae729 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.
|
|
Android51
The runner has received a shutdown signal. This can happen when the runner service is stopped, or a manually started runner is canceled.
|
|
Linux51
The runner has received a shutdown signal. This can happen when the runner service is stopped, or a manually started runner is canceled.
|
|
Android51
The self-hosted runner: i-0a03dda29c6f2a15c 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.
|
|
Linux51
The self-hosted runner: i-06017226b053653ec 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.
|
|
Android52
The runner has received a shutdown signal. This can happen when the runner service is stopped, or a manually started runner is canceled.
|
|
Android52
The self-hosted runner: i-0c50ec0bfb5069f35 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.
|
|
Windows51 / build
The runner has received a shutdown signal. This can happen when the runner service is stopped, or a manually started runner is canceled.
|
|
Windows51 / build
The self-hosted runner: i-016c6f622c5d760ed 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.
|
Artifacts
Produced during runtime
| Name | Size | |
|---|---|---|
|
CesiumForUnreal-50-ios-v1.30.1-6-gf9070951
Expired
|
402 MB |
|
|
CesiumForUnreal-50-macos-v1.30.1-6-gf9070951
Expired
|
262 MB |
|
|
CesiumForUnreal-51-ios-v1.30.1-6-gf9070951
Expired
|
437 MB |
|
|
CesiumForUnreal-51-macos-v1.30.1-6-gf9070951
Expired
|
287 MB |
|
|
CesiumForUnreal-52-ios-v1.30.1-6-gf9070951
Expired
|
270 MB |
|
|
CesiumForUnreal-52-linux-v1.30.1-6-gf9070951
Expired
|
220 MB |
|
|
CesiumForUnreal-52-macos-v1.30.1-6-gf9070951
Expired
|
276 MB |
|