Erigon CI Skill

Orchestrates CI verification: run test groups locally and/or dispatch GitHub Actions on any branch.

Each test group has its own dedicated skill for drill-down on failures. Use those when a specific group fails and you need to re-run individual tests.

Local Test Groups

make test-all no longer covers the EEST spec tests or the cl/spectest consensus spec test — run those via their dedicated targets above when relevant.

Pitfall: prefer make eest-spec-<shard> over bash tools/run-eest-spec-test.sh <shard>. The make target lists evm / evm.race as a prereq so stale binaries get rebuilt; the script invoked directly does not, and a stale binary against current fixtures will inflate failures or hide regressions.

Lint (run first — non-deterministic, may need multiple runs)

make lint

Quick gate (before pushing a fix)

make lint && make test-short

Full gate (before marking PR ready for review)

make lint && make erigon integration && GOGC=80 make test-all

Race check (for concurrency-sensitive changes)

make lint && make test-all-race

Part 2: Remote Dispatch (trigger CI on any branch)

Use gh workflow run to trigger workflows on a branch. Required for branches not targeting main (e.g. bal-devnet-2).

Dispatch all workflows on a branch

BRANCH=$(git branch --show-current)  # or set explicitly: BRANCH="bal-devnet-2"

for wf in \
  "Unit tests" \
  "All tests" \
  "EEST spec tests" \
  "Lint" \
  "Test Hive" \
  "Kurtosis Assertoor GitHub Action" \
  "QA - RPC Integration Tests" \
  "QA - RPC Integration Tests Remote" \
  "QA - RPC Integration Tests (Gnosis)" \
  "Windows downloader tests"; do
  echo "Dispatching: $wf"
  gh workflow run "$wf" --ref $BRANCH
done

Workflow dispatch support

Note: Consensus spec has no workflow_dispatch — only fires on pull_request events targeting main/release.

Monitor runs

BRANCH=$(git branch --show-current)
gh run list --branch $BRANCH --limit 15

Check for failures:

gh run list --branch $BRANCH --limit 20 | grep -E "failure|cancelled"

Watch a specific run:

gh run watch <run-id>

Part 3: Full CI Gate (local + remote)

When preparing a devnet/feature branch for review:

1. Local gate — fast feedback before pushing:

   make lint && make erigon integration && make test-short
   

2. Push branch:

   git push origin <branch>
   

3. Dispatch all remote workflows (use the loop from Part 2).

4. Monitor until all pass:

   gh run list --branch $(git branch --show-current) --limit 15
   

5. Race check (for concurrency-heavy changes):

   make test-all-race