Skip to content

celo-monorepo tests #448

celo-monorepo tests

celo-monorepo tests #448

Triggered via pull request August 2, 2023 09:37
Status Failure
Total duration 1h 6m 10s
Artifacts

circleci.yml

on: pull_request
Install dependencies
2m 19s
Install dependencies
ContractKit Tests
3m 57s
ContractKit Tests
Protocol Tests Prepare
5m 44s
Protocol Tests Prepare
General jest test
1m 57s
General jest test
Wallet test
48s
Wallet test
CeloCli Tests
4m 29s
CeloCli Tests
Typescript package Tests
32s
Typescript package Tests
SDK Base package Tests
30s
SDK Base package Tests
SDK Utils package Tests
34s
SDK Utils package Tests
Matrix: certora-test
Matrix: protocol-test-matrix
Identity Tests
2m 28s
Identity Tests
Transaction URI Tests
3m 46s
Transaction URI Tests
Matrix: end-to-end-geth-matrix
Protocol Test Release
2m 5s
Protocol Test Release
Fit to window
Zoom out
Zoom in

Annotations

5 errors and 3 warnings
CeloCli Tests
Process completed with exit code 1.
e2e Replica test
The self-hosted runner: k8s-hosted-runners-monorepo-node18-8bfz5-w9rcn 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 Governance Validators
The self-hosted runner: k8s-hosted-runners-monorepo-node18-8bfz5-496bz 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-8bfz5-75wkw 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 Identity
The self-hosted runner: k8s-hosted-runners-monorepo-node18-8bfz5-llbc4 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.
Protocol Governance Validators
Attempt 1 failed. Reason: Child_process exited with error code 1
Protocol Common tests
Attempt 1 failed. Reason: Timeout of 1800000ms hit