Skip to content

feat(cli): add offline block-building benchmark subcommand #2286

feat(cli): add offline block-building benchmark subcommand

feat(cli): add offline block-building benchmark subcommand #2286

Workflow file for this run

name: CI
on:
push:
branches: [main]
pull_request:
branches: ["**"]
merge_group:
workflow_dispatch:
# Cancel in-progress runs when a new commit is pushed to the same PR or branch
concurrency:
group: ${{ github.workflow }}-${{ github.head_ref || github.run_id }}
cancel-in-progress: true
env:
CARGO_NET_GIT_FETCH_WITH_CLI: "true"
CARGO_NET_RETRY: "10"
jobs:
lint:
name: Lint
runs-on: ubuntu-latest
steps:
- uses: actions/checkout@v6
- name: Setup Rust
uses: dtolnay/rust-toolchain@master
with:
toolchain: "1.97.1"
components: rustfmt, clippy
- name: Setup cache
# Tools under tooling/ are separate Cargo workspaces with their own
# target dir and Cargo.lock, so they need listing explicitly or their
# builds are neither cached nor reflected in the cache key.
uses: Swatinem/rust-cache@v2
with:
workspaces: |
.
tooling/event-monitor
- name: Check formatting
run: cargo fmt --all -- --check
- name: Cargo check
run: cargo check --workspace --all-targets
- name: Clippy
run: cargo clippy --workspace --all-targets -- -D warnings
# tooling/event-monitor declares its own [workspace] table, so every step
# above stops at the root workspace members and never reaches it. Its
# tests run in this job rather than in `test` because clippy has already
# compiled the test targets, and because they need none of that job's
# leanSpec fixtures.
# `--locked` so the committed Cargo.lock is actually enforced: without it
# cargo silently resolves and rewrites the lockfile in CI, and a stale or
# missing entry never fails the build.
- name: Lint tooling
working-directory: tooling/event-monitor
run: |
cargo fmt --all -- --check
cargo clippy --locked --all-targets -- -D warnings
- name: Test tooling
working-directory: tooling/event-monitor
run: cargo test --locked
test:
name: Test
runs-on: ubuntu-latest
steps:
- uses: actions/checkout@v6
- name: Run fixture-based tests
uses: ./.github/actions/run-fixture-tests
# Reuses the release build from the test step; validates the benchmark
# harness end-to-end and its JSON output contract in a few seconds.
- name: Benchmark smoke (mock crypto)
run: |
cargo run --release --bin ethlambda -- benchmark synthetic --mock-crypto \
--num-validators 4 --warmup-slots 4 --iterations 3 --format json \
| jq -e '.schema_version == 1 and (.samples | length == 3)'