Skip to content
test-suite

add lockbud to ci #77

Sign in to view logs

add lockbud to ci

add lockbud to ci #77

Triggered via pull request October 6, 2024 22:01
@eserileveserilev
synchronize #9
lockbud-ci
Status Failure
Total duration 1h 24m 22s
Artifacts 1

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 6s
check-code
check-msrv
5m 23s
check-msrv
lockbud
1m 7s
lockbud
release-tests-ubuntu
1h 3m
release-tests-ubuntu
release-tests-windows
1h 23m
release-tests-windows
beacon-chain-tests
56m 51s
beacon-chain-tests
op-pool-tests
15m 32s
op-pool-tests
network-tests
18m 31s
network-tests
slasher-tests
1m 42s
slasher-tests
debug-tests-ubuntu
9m 13s
debug-tests-ubuntu
state-transition-vectors-ubuntu
2m 15s
state-transition-vectors-ubuntu
ef-tests-ubuntu
13m 16s
ef-tests-ubuntu
basic-simulator-ubuntu
13m 16s
basic-simulator-ubuntu
fallback-simulator-ubuntu
11m 41s
fallback-simulator-ubuntu
execution-engine-integration-ubuntu
11m 42s
execution-engine-integration-ubuntu
cargo-udeps
17s
cargo-udeps
compile-with-beta-compiler
14m 3s
compile-with-beta-compiler
cli-check
16m 3s
cli-check
test-suite-success
0s
test-suite-success
Fit to window
Zoom out
Zoom in

Annotations

3 errors and 1 warning
cargo-udeps
Process completed with exit code 2.
lockbud
Process completed with exit code 101.
execution-engine-integration-ubuntu
Process completed with exit code 2.
lockbud
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/

Artifacts

Produced during runtime
Name Size
network_test_logs Expired
369 KB