菜单
Run QA RPC Integration Tests locally against a synced Erigon datadir, or dispatch them remotely via GitHub Actions. Tests compare rpcdaemon JSON-RPC responses against expected results from erigontech/rpc-tests.
默认使用会先检查来源的 Prompt；你也可以切换为直接命令，或下载本地副本。
决定是否安装前，请先阅读 SKILL.md，以及 SkillsMP 当前展示的配套文件。
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
直接命令不会经过审查 Prompt；运行前请先检查来源。
npx skills add https://github.com/erigontech/erigon --skill erigon-test-rpc命令会保持在同一行。复制前请横向滚动并检查完整内容。
想先保存到本地？可下载 SkillsMP 当前能够提供的文件。
Compact an existing MDBX database instance to reclaim free/reclaimable space. Use this when the user wants to shrink mdbx.dat, reclaim MDBX garbage-collected pages, or fix MDBX_MAP_FULL issues.
Read and interpret the results, logs and artifacts of Erigon's QA workflows (the `qa-*.yml` GitHub Actions workflows - tip tracking, sync from scratch, exec from zero, snapshot download, clean exit, RPC integration/performance). Use when asked why a QA test failed, what a QA run measured, how to read a QA test log, what "Deadline reached" / "total sync time below threshold" / "exec_steps_in_db exceeded threshold" / a state-snapshot hash mismatch mean, or when triaging a red `QA - ...` check on a PR or release branch.
Run repeatable benchmarkoor performance benchmarks against Erigon on current and future devnets, using protected native Linux OverlayFS with either pristine State Actor datadirs or pre-populated snapshots. Use for generic benchmark testing, compute or stateful suites, first-time setup, local client image overrides, pristine-state protection, result extraction, before/after MGas/s comparisons, and cross-client ranking tables.
基于 SOC 职业分类
正在显示 SKILL.md
| name | erigon-test-rpc |
| description | Run QA RPC Integration Tests locally against a synced Erigon datadir, or dispatch them remotely via GitHub Actions. Tests compare rpcdaemon JSON-RPC responses against expected results from erigontech/rpc-tests. |
Tests that run rpcdaemon against a pre-synced Erigon datadir and compare JSON-RPC responses against golden expected outputs from the erigontech/rpc-tests repository.
rpcdaemon and integration binaries built (make rpcdaemon integration)The CI workflow:
integration run_migrations to apply pending migrationsrpcdaemon --datadir <reference-datadir>run_rpc_tests.sh which clones erigontech/rpc-tests, sets up a Python venv, and runs run_tests.py against port 8545The backup/restore pattern exists because run_migrations writes to the DB.
# Point to your synced mainnet Erigon node
export ERIGON_REFERENCE_DATA_DIR=/path/to/your/erigon/mainnet-datadir
# Optional: workspace for test output
export WORKSPACE=/tmp/rpc-test-run
mkdir -p $WORKSPACE
cp -r $ERIGON_REFERENCE_DATA_DIR/chaindata /tmp/chaindata-backup
make rpcdaemon integration
./build/bin/integration run_migrations --datadir $ERIGON_REFERENCE_DATA_DIR --chain mainnet
./build/bin/rpcdaemon --datadir $ERIGON_REFERENCE_DATA_DIR \
--http.api admin,debug,eth,parity,erigon,trace,web3,txpool,ots,net \
--ws > /tmp/rpcdaemon.log 2>&1 &
RPC_DAEMON_PID=$!
# Wait for port 8545
for i in {1..30}; do
nc -z localhost 8545 && break || sleep 5
done
.github/workflows/scripts/run_rpc_tests_ethereum.sh $WORKSPACE /tmp/rpc-results
echo "Exit: $?"
kill $RPC_DAEMON_PID
# Restore original chaindata
rm -rf $ERIGON_REFERENCE_DATA_DIR/chaindata
mv /tmp/chaindata-backup $ERIGON_REFERENCE_DATA_DIR/chaindata
Clone rpc-tests and run one test directly:
git clone --depth 1 --branch v1.121.0 https://github.com/erigontech/rpc-tests /tmp/rpc-tests
cd /tmp/rpc-tests
python3 -m venv .venv && source .venv/bin/activate
pip3 install -r requirements.txt
cd integration
# Run just one test
python3 run_tests.py --blockchain mainnet --port 8545 \
--include-api-list eth_getBlockByNumber/test_1.json \
--display-only-fail --json-diff
The runner outputs diffs for failing tests. Each test is a .json file in the integration/<chain>/ directory of rpc-tests. To investigate:
# Show which tests failed
grep "FAILED\|PASS\|SKIP" /tmp/rpc-results/output.log | grep FAIL
# Re-run just the failing API group
cd /tmp/rpc-tests/integration
python3 run_tests.py --blockchain mainnet --port 8545 \
--include-api-list eth_getBlockByNumber \
--display-only-fail --json-diff
# Run with full response dump to see what rpcdaemon returned
python3 run_tests.py --blockchain mainnet --port 8545 \
--include-api-list eth_getBlockByNumber/test_1.json \
--dump-response
Some tests are intentionally disabled in the CI run (see run_rpc_tests_ethereum.sh). These include:
net_peerCount, admin_peers, etc.)| Variant | CI workflow | File |
|---|---|---|
| Mainnet | QA - RPC Integration Tests | qa-rpc-integration-tests.yml |
| Latest blocks | QA - RPC Integration Tests Remote | qa-rpc-integration-tests-remote.yml |
| Gnosis | QA - RPC Integration Tests (Gnosis) | qa-rpc-integration-tests-gnosis.yml |
Remote dispatch:
gh workflow run "QA - RPC Integration Tests" --ref <branch>
gh workflow run "QA - RPC Integration Tests Remote" --ref <branch>
gh workflow run "QA - RPC Integration Tests (Gnosis)" --ref <branch>
The CI runner maintains a pre-synced mainnet datadir at /opt/erigon-versions/reference-version/datadir. To create a local equivalent:
ERIGON_REFERENCE_DATA_DIR to that datadirA full mainnet sync takes ~2-4 days on NVMe with --prune.mode=minimal. Alternatively, ask the team for a snapshot of the reference datadir.