Add Experimental QUIC support (#4577) #13697
You are viewing an older attempt in the history of this workflow run.
View latest attempt.
bors[bot]test-suite.yml
on: push
cargo-fmt
13s
extract-msrv
6s
target-branch-check
0s
compile-with-beta-compiler
22m 8s
release-tests-ubuntu
0s
release-tests-windows
34m 54s
beacon-chain-tests
15m 53s
op-pool-tests
23m 20s
slasher-tests
4m 36s
debug-tests-ubuntu
17m 13s
state-transition-vectors-ubuntu
19m 2s
ef-tests-ubuntu
15m 34s
dockerfile-ubuntu
34m 55s
eth1-simulator-ubuntu
39m 38s
merge-transition-ubuntu
39m 6s
no-eth1-simulator-ubuntu
39m 49s
syncing-simulator-ubuntu
39m 27s
doppelganger-protection-test
45m 14s
execution-engine-integration-ubuntu
22m 57s
check-benchmarks
8m 56s
clippy
9m 26s
arbitrary-check
1m 22s
cargo-audit
6m 13s
cargo-vendor
42s
cargo-udeps
16m 20s
check-msrv
11m 21s
Annotations
3 errors
|
release-tests-ubuntu
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-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
The self-hosted runner: runner-win-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.
|