Build & Integration Tests: martinvol/applyMigrationsGethFails #4614
martinvolcelo-monorepo.yml
on: pull_request
Install dependencies
4m 25s
Protocol Test Release
13m 18s
Matrix: certora-test
Matrix: end-to-end-geth-matrix
Matrix: protocol-test-matrix
Annotations
15 errors and 3 warnings
|
Protocol Common tests
The self-hosted runner: k8s-hosted-runners-monorepo-7g9wp-8cwlm 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 Test Release
The self-hosted runner: k8s-hosted-runners-monorepo-7g9wp-fcj48 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 Blockchain Parameters test
The self-hosted runner: k8s-hosted-runners-monorepo-7g9wp-7kdjx 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 Governance test
The self-hosted runner: k8s-hosted-runners-monorepo-7g9wp-wp22t 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-7g9wp-ldlrg 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 runner has received a shutdown signal. This can happen when the runner service is stopped, or a manually started runner is canceled.
|
|
Protocol Compatibility
The operation was canceled.
|
|
e2e Slashing test
The runner has received a shutdown signal. This can happen when the runner service is stopped, or a manually started runner is canceled.
|
|
e2e Slashing test
The operation was canceled.
|
|
e2e Validator order test
The runner has received a shutdown signal. This can happen when the runner service is stopped, or a manually started runner is canceled.
|
|
e2e Validator order test
The operation was canceled.
|
|
e2e Sync test
The runner has received a shutdown signal. This can happen when the runner service is stopped, or a manually started runner is canceled.
|
|
e2e Sync test
The operation was canceled.
|
|
e2e Transfer test
The runner has received a shutdown signal. This can happen when the runner service is stopped, or a manually started runner is canceled.
|
|
e2e Transfer test
The operation was canceled.
|
|
e2e Validator order test
Attempt 1 failed. Reason: Timeout of 1800000ms hit
|
|
e2e Sync test
Attempt 1 failed. Reason: Timeout of 1800000ms hit
|
|
e2e Transfer test
Attempt 1 failed. Reason: Timeout of 1800000ms hit
|