fix: block sync hangs on initial node start · lambdaclass/lambda_ethereum_consensus@9d6eecf

Triggered via pull request October 2, 2024 21:58

rodrigo-o

synchronize #1314

sync-issues-on-initial-node-run

Status Cancelled

Total duration 5m 32s

Artifacts –

ci.yml

on: pull_request

Build native libraries

11s

Download Beacon Node OAPI

Start and stop the node

3m 43s

Test

3m 39s

Matrix: Run spec-tests

All spec-tests passed

0s

Annotations

11 errors and 7 warnings

Lint

Process completed with exit code 8.

Build project

Canceling since a higher priority waiting request for 'CI-refs/pull/1314/merge' exists

Build Docker image

Canceling since a higher priority waiting request for 'CI-refs/pull/1314/merge' exists

Build Docker image

The operation was canceled.

Run spec-tests (deneb, mainnet)

Canceling since a higher priority waiting request for 'CI-refs/pull/1314/merge' exists

Run spec-tests (deneb, mainnet)

The operation was canceled.

Run spec-tests (deneb, general)

Canceling since a higher priority waiting request for 'CI-refs/pull/1314/merge' exists

Run spec-tests (deneb, minimal)

Canceling since a higher priority waiting request for 'CI-refs/pull/1314/merge' exists

Run spec-tests (deneb, minimal)

The operation was canceled.

Run spec-tests (deneb, general)

The operation was canceled.

All spec-tests passed

Process completed with exit code 1.

Lint: lib/lambda_ethereum_consensus/p2p/peerbook.ex#L127

Function body is nested too deep (max depth is 2, was 3).

Test