Release v4.5.0 (#4768) #13949
bors[bot]test-suite.yml
on: push
cargo-fmt
19s
extract-msrv
4s
target-branch-check
0s
compile-with-beta-compiler
20m 45s
release-tests-ubuntu
14m 53s
release-tests-windows
14m 55s
beacon-chain-tests
14m 53s
op-pool-tests
23m 1s
slasher-tests
6m 14s
debug-tests-ubuntu
14m 53s
state-transition-vectors-ubuntu
13m 59s
ef-tests-ubuntu
14m 52s
dockerfile-ubuntu
26m 32s
eth1-simulator-ubuntu
32m 58s
merge-transition-ubuntu
33m 1s
no-eth1-simulator-ubuntu
33m 0s
syncing-simulator-ubuntu
32m 6s
doppelganger-protection-test
32m 57s
execution-engine-integration-ubuntu
22m 15s
check-benchmarks
8m 6s
clippy
9m 3s
arbitrary-check
1m 42s
cargo-audit
5m 22s
cargo-vendor
33s
cargo-udeps
17m 39s
check-msrv
10m 30s
Annotations
15 errors
|
ef-tests-ubuntu
The self-hosted runner: runner-small-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.
|
|
beacon-chain-tests
The self-hosted runner: runner-large-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.
|
|
release-tests-ubuntu
The self-hosted runner: runner-large-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.
|
|
debug-tests-ubuntu
The self-hosted runner: runner-large-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.
|
|
release-tests-windows
The runner has received a shutdown signal. This can happen when the runner service is stopped, or a manually started runner is canceled.
|
|
release-tests-windows
Canceling since a higher priority waiting request for 'test-suite-refs/heads/staging' exists
|
|
release-tests-windows
The self-hosted runner: runner-win-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.
|
|
eth1-simulator-ubuntu
Canceling since a higher priority waiting request for 'test-suite-refs/heads/staging' exists
|
|
eth1-simulator-ubuntu
The operation was canceled.
|
|
doppelganger-protection-test
Canceling since a higher priority waiting request for 'test-suite-refs/heads/staging' exists
|
|
doppelganger-protection-test
The operation was canceled.
|
|
merge-transition-ubuntu
Canceling since a higher priority waiting request for 'test-suite-refs/heads/staging' exists
|
|
merge-transition-ubuntu
The operation was canceled.
|
|
no-eth1-simulator-ubuntu
Canceling since a higher priority waiting request for 'test-suite-refs/heads/staging' exists
|
|
no-eth1-simulator-ubuntu
The operation was canceled.
|