Skip to content
Build and test

Self host runner #328

Sign in to view logs

Self host runner

Self host runner #328

Triggered via pull request September 9, 2023 03:43
@SuZhou-JoeSuZhou-Joe
synchronize #3
self-host-runner
Status Failure
Total duration 1d 4h 17m 3s
Artifacts 12
This run and associated checks have been archived and are scheduled for deletion. Learn more about checks retention

build_and_test_workflow.yml

on: pull_request
Matrix: build-min-artifact-tests
Matrix: build-lint-test
Matrix: functional-tests
Matrix: Run backwards compatibility tests
Fit to window
Zoom out
Zoom in

Annotations

37 errors
Run functional tests on Windows (ciGroup10)
Process completed with exit code 1.
Run functional tests on Windows (ciGroup2)
Process completed with exit code 1.
Run functional tests on Windows (ciGroup11)
Process completed with exit code 1.
Run functional tests on Windows (ciGroup12)
Process completed with exit code 1.
Run functional tests on Windows (ciGroup9)
Process completed with exit code 1.
Run functional tests on Windows (ciGroup8)
Process completed with exit code 1.
Run functional tests on Windows (ciGroup6)
Process completed with exit code 1.
Run functional tests on Linux (ciGroup1)
Process completed with exit code 1.
Run functional tests on Windows (ciGroup7)
Process completed with exit code 1.
Build min release artifacts on Linux ARM64
The template is not valid. .github/workflows/build_and_test_workflow.yml (Line: 272, Col: 16): hashFiles('**/yarn.lock') couldn't finish within 120 seconds.
Build min release artifacts on Linux x64
The job was canceled because "self-hosted_Linux_ARM64_t" failed.
Build min release artifacts on Linux x64
The template is not valid. .github/workflows/build_and_test_workflow.yml (Line: 272, Col: 16): hashFiles('**/yarn.lock') couldn't finish within 120 seconds.
Run functional tests on Linux (ciGroup11)
Process completed with exit code 1.
Run functional tests on Linux (ciGroup10)
Process completed with exit code 1.
Run functional tests on Linux (ciGroup12)
Process completed with exit code 1.
Run functional tests on Linux (ciGroup13)
Process completed with exit code 1.
Run functional tests on Linux (ciGroup3)
The runner has received a shutdown signal. This can happen when the runner service is stopped, or a manually started runner is canceled.
Run functional tests on Linux (ciGroup3)
The operation was canceled.
Run functional tests on Linux (ciGroup7)
The runner has received a shutdown signal. This can happen when the runner service is stopped, or a manually started runner is canceled.
Run functional tests on Linux (ciGroup7)
The operation was canceled.
Run functional tests on Linux (ciGroup7)
Process completed with exit code 143.
Run functional tests on Linux (ciGroup6)
The runner has received a shutdown signal. This can happen when the runner service is stopped, or a manually started runner is canceled.
Run functional tests on Linux (ciGroup6)
The operation was canceled.
Run functional tests on Linux (ciGroup5)
The runner has received a shutdown signal. This can happen when the runner service is stopped, or a manually started runner is canceled.
Run functional tests on Linux (ciGroup5)
The operation was canceled.
Run functional tests on Linux (ciGroup5)
Process completed with exit code 143.
Run functional tests on Linux (ciGroup4)
The runner has received a shutdown signal. This can happen when the runner service is stopped, or a manually started runner is canceled.
Run functional tests on Linux (ciGroup4)
Process completed with exit code 143.
Run functional tests on Linux (ciGroup4)
The operation was canceled.
Run functional tests on Linux (ciGroup2)
The runner has received a shutdown signal. This can happen when the runner service is stopped, or a manually started runner is canceled.
Run functional tests on Linux (ciGroup2)
The operation was canceled.
Build and Verify on Linux (ciGroup1)
The self-hosted runner: my-runner-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.
Build and Verify on Linux (ciGroup3)
The self-hosted runner: my-runner-4 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.
Run functional tests on Linux (ciGroup9)
The self-hosted runner: my-runner-6 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.
Build and Verify on Linux (ciGroup2)
The self-hosted runner: my-runner-3 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.
Run functional tests on Linux (ciGroup8)
The self-hosted runner: my-runner-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.
Build and Verify on Linux (ciGroup4)
This request was automatically failed because there were no enabled runners online to process the request for more than 1 days.

Artifacts

Produced during runtime
Name Size
failure-artifacts-ci1 Expired
321 KB
failure-artifacts-ci10 Expired
321 KB
failure-artifacts-ci11 Expired
4.6 MB
failure-artifacts-ci12 Expired
3.92 MB
failure-artifacts-ci13 Expired
321 KB
failure-artifacts-ci2 Expired
5.72 MB
failure-artifacts-ci6 Expired
13.4 MB
failure-artifacts-ci7 Expired
79.4 MB
failure-artifacts-ci8 Expired
15.6 MB
failure-artifacts-ci9 Expired
7.52 MB
linux-arm64-3.0.0 Expired
143 MB
linux-x64-3.0.0 Expired
143 MB