Skip to content

add lockbud to ci

add lockbud to ci #49

Triggered via pull request September 19, 2024 18:55
@eserileveserilev
synchronize #9
lockbud-ci
Status Failure
Total duration 1h 14m 41s
Artifacts

test-suite.yml

on: pull_request
Check for 'skip-ci' label
0s
Check for 'skip-ci' label
target-branch-check
0s
target-branch-check
check-code
9m 9s
check-code
check-msrv
5m 4s
check-msrv
release-tests-ubuntu
54m 29s
release-tests-ubuntu
release-tests-windows
1h 13m
release-tests-windows
beacon-chain-tests
34m 41s
beacon-chain-tests
op-pool-tests
12m 23s
op-pool-tests
network-tests
9m 41s
network-tests
slasher-tests
1m 45s
slasher-tests
debug-tests-ubuntu
9m 31s
debug-tests-ubuntu
state-transition-vectors-ubuntu
2m 26s
state-transition-vectors-ubuntu
ef-tests-ubuntu
12m 26s
ef-tests-ubuntu
basic-simulator-ubuntu
13m 27s
basic-simulator-ubuntu
fallback-simulator-ubuntu
10m 53s
fallback-simulator-ubuntu
execution-engine-integration-ubuntu
47m 38s
execution-engine-integration-ubuntu
cargo-udeps
7m 21s
cargo-udeps
compile-with-beta-compiler
13m 41s
compile-with-beta-compiler
cli-check
8m 16s
cli-check
test-suite-success
0s
test-suite-success
Fit to window
Zoom out
Zoom in

Annotations

3 errors
lockbud
Process completed with exit code 2.
execution-engine-integration-ubuntu
The hosted runner: GitHub Actions 15 lost communication with the server. 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
Process completed with exit code 2.