Skip to content

Detect invalid proposer signature on RPC block processing #19104

Detect invalid proposer signature on RPC block processing

Detect invalid proposer signature on RPC block processing #19104

Triggered via pull request November 21, 2024 10:27
Status Success
Total duration 50m 8s
Artifacts 1

test-suite.yml

on: pull_request
release-tests-ubuntu
40m 57s
release-tests-ubuntu
release-tests-windows
49m 24s
release-tests-windows
beacon-chain-tests
18m 38s
beacon-chain-tests
op-pool-tests
23m 32s
op-pool-tests
network-tests
25m 44s
network-tests
slasher-tests
3m 30s
slasher-tests
debug-tests-ubuntu
6m 9s
debug-tests-ubuntu
state-transition-vectors-ubuntu
9m 37s
state-transition-vectors-ubuntu
ef-tests-ubuntu
18m 29s
ef-tests-ubuntu
basic-simulator-ubuntu
20m 53s
basic-simulator-ubuntu
fallback-simulator-ubuntu
20m 42s
fallback-simulator-ubuntu
execution-engine-integration-ubuntu
8m 6s
execution-engine-integration-ubuntu
cargo-udeps
7m 11s
cargo-udeps
compile-with-beta-compiler
15m 52s
compile-with-beta-compiler
cli-check
14m 35s
cli-check
test-suite-success
7s
test-suite-success
Fit to window
Zoom out
Zoom in

Annotations

1 warning
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
291 KB