Skip to content

celo-monorepo tests #1031

celo-monorepo tests

celo-monorepo tests #1031

Triggered via push September 25, 2023 09:07
Status Failure
Total duration 39m 33s
Artifacts

circleci.yml

on: push
Install dependencies
2m 33s
Install dependencies
ContractKit Tests
4m 20s
ContractKit Tests
Protocol Tests Prepare
15m 9s
Protocol Tests Prepare
General jest test
7m 7s
General jest test
Wallet test
1m 1s
Wallet test
CeloCli Tests
4m 23s
CeloCli Tests
Typescript package Tests
0s
Typescript package Tests
SDK Base package Tests
38s
SDK Base package Tests
SDK Utils package Tests
44s
SDK Utils package Tests
Matrix: certora-test
Matrix: protocol-test-matrix
Identity Tests
11m 6s
Identity Tests
Transaction URI Tests
2m 53s
Transaction URI Tests
Matrix: end-to-end-geth-matrix
Protocol Test Release
0s
Protocol Test Release
Fit to window
Zoom out
Zoom in

Annotations

7 errors and 2 warnings
Protocol Tests Prepare
The self-hosted runner: k8s-hosted-runners-monorepo-node18-8mmnr-slwj7 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.
Protocol Compatibility
The self-hosted runner: k8s-hosted-runners-monorepo-node18-8mmnr-6j6v9 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.
ODIS test
The self-hosted runner: k8s-hosted-runners-monorepo-node18-8mmnr-vctsg 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.
Identity Tests
The self-hosted runner: k8s-hosted-runners-monorepo-node18-8mmnr-zgdg9 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.
e2e CIP35 eth compatibility test
The self-hosted runner: k8s-hosted-runners-monorepo-node18-8mmnr-dj5gt 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.
e2e Validator order test
The self-hosted runner: k8s-hosted-runners-monorepo-node18-8mmnr-s6x4w 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.
e2e Sync test
The self-hosted runner: k8s-hosted-runners-monorepo-node18-8mmnr-jtj59 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.
General jest test
No files were found with the provided path: test-results/jest. No artifacts will be uploaded.
e2e Governance test
Attempt 1 failed. Reason: Child_process exited with error code 3