Skip to content

celo-monorepo tests #415

celo-monorepo tests

celo-monorepo tests #415

Triggered via push July 27, 2023 19:40
Status Failure
Total duration 41m 4s
Artifacts

circleci.yml

on: push
Install dependencies
5m 57s
Install dependencies
ContractKit Tests
5m 5s
ContractKit Tests
Protocol Tests Prepare
6m 30s
Protocol Tests Prepare
General jest test
1m 52s
General jest test
Wallet test
51s
Wallet test
CeloCli Tests
5m 54s
CeloCli Tests
Typescript package Tests
32s
Typescript package Tests
SDK Base package Tests
29s
SDK Base package Tests
SDK Utils package Tests
40s
SDK Utils package Tests
Matrix: certora-test
Matrix: protocol-test-matrix
Identity Tests
2m 59s
Identity Tests
Transaction URI Tests
4m 24s
Transaction URI Tests
Matrix: end-to-end-geth-matrix
Protocol Test Release
2m 51s
Protocol Test Release
Fit to window
Zoom out
Zoom in

Annotations

8 errors and 1 warning
CeloCli Tests
Process completed with exit code 1.
Protocol Common tests
The self-hosted runner: k8s-hosted-runners-monorepo-9j2jp-xbvkg 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-9j2jp-p946t 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 Voting
The self-hosted runner: k8s-hosted-runners-monorepo-9j2jp-dxkzt 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-9j2jp-5p6bm 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 Replica test
The self-hosted runner: k8s-hosted-runners-monorepo-9j2jp-fb6x5 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 Slashing test
The self-hosted runner: k8s-hosted-runners-monorepo-9j2jp-cxvlq 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-9j2jp-vvctb 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.