Skip to content

feat: update

feat: update #327

Re-run triggered September 11, 2023 02:09
Status Failure
Total duration 2h 6m 37s
Artifacts 13
This run and associated checks have been archived and are scheduled for deletion. Learn more about checks retention
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

35 errors
Build and Verify on Linux (ciGroup1)
The runner has received a shutdown signal. This can happen when the runner service is stopped, or a manually started runner is canceled.
Build and Verify on Linux (ciGroup1)
The operation was canceled.
Build and Verify on Linux (ciGroup3)
The self-hosted runner: my-runner-test-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 (ciGroup2)
Process completed with exit code 1.
Run functional tests on Linux (ciGroup2)
Process completed with exit code 1.
Build and Verify on Linux (ciGroup4)
Process completed with exit code 1.
Run functional tests on Windows (ciGroup2)
Process completed with exit code 1.
Run functional tests on Linux (ciGroup5)
Process completed with exit code 1.
Run functional tests on Windows (ciGroup9)
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 (ciGroup6)
Process completed with exit code 1.
Run functional tests on Windows (ciGroup8)
Process completed with exit code 1.
Run functional tests on Linux (ciGroup12)
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 (ciGroup12)
The operation was canceled.
Run functional tests on Linux (ciGroup10)
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 (ciGroup10)
The operation was canceled.
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 (ciGroup11)
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 (ciGroup11)
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 backwards compatibility tests (osd-2.1.0)
The self-hosted runner: my-runner-2 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 (ciGroup13)
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.
Run functional tests on Linux (ciGroup9)
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 backwards compatibility tests (osd-2.0.0)
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.
Run backwards compatibility tests (osd-2.2.0)
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.
Run functional tests on Linux (ciGroup8)
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 backwards compatibility tests (osd-2.3.0)
The job was canceled because "osd-2_1_0" failed.
Run backwards compatibility tests (osd-2.5.0)
The job was canceled because "osd-2_1_0" failed.
Run backwards compatibility tests (osd-2.4.0)
The job was canceled because "osd-2_1_0" failed.
Run backwards compatibility tests (osd-2.6.0)
The job was canceled because "osd-2_1_0" failed.
Run backwards compatibility tests (osd-2.7.0)
The job was canceled because "osd-2_1_0" failed.
Run functional tests on Windows (ciGroup7)
Process completed with exit code 1.

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-ci3 Expired
321 KB
failure-artifacts-ci4 Expired
321 KB
failure-artifacts-ci5 Expired
2.05 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