Run the evm-wallet Docker e2e tests (build, start stack, wait for healthy, test, diagnose failures).
70
85%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
View guide
Passed
No findings from the security scan
Run all commands from the repo root unless noted.
docker info 2>&1 | head -5If it fails, tell the user Docker is not running and ask them to start Docker Desktop (or the daemon), then wait for confirmation before continuing.
yarn workspace @ocap/evm-wallet-experiment docker:build 2>&1 | tail -30This builds the full monorepo then builds the Docker images. It may take a few minutes. Report any errors from the tail output.
Always bring the stack down first to avoid stale container state (e.g. spent delegation budgets from a previous run leaking into the new run).
yarn workspace @ocap/evm-wallet-experiment docker:down 2>&1 | tail -10Then start the stack:
yarn workspace @ocap/evm-wallet-experiment docker:ensure-logs && \
yarn workspace @ocap/evm-wallet-experiment docker:compose up -d 2>&1 | tail -20Poll every 10 seconds (up to 3 minutes / 18 attempts). All 8 services must reach (healthy) status before proceeding:
evm, bundlerkernel-home-bundler-7702, kernel-away-bundler-7702kernel-home-bundler-hybrid, kernel-away-bundler-hybridkernel-home-peer-relay, kernel-away-peer-relayi=0; while [ $i -lt 18 ]; do
i=$((i+1))
ps_out=$(yarn workspace @ocap/evm-wallet-experiment docker:ps 2>&1)
healthy=$(echo "$ps_out" | grep -c "(healthy)" || true)
echo "Attempt $i/18: $healthy/8 healthy"
if [ "$healthy" -ge 8 ]; then echo "Stack ready."; break; fi
if [ "$i" -eq 18 ]; then echo "Timed out:"; echo "$ps_out"; exit 1; fi
sleep 10
doneIf the loop exits with a timeout, show the last docker:ps output and stop — do not proceed to the tests.
yarn workspace @ocap/evm-wallet-experiment test:e2e:docker 2>&1 | tail -80The vitest reporter also writes structured results to packages/evm-wallet-experiment/logs/test-results.json.
If tests fail, investigate in this order:
cat packages/evm-wallet-experiment/logs/test-results.jsonLook at the testResults array for failed tests and their error messages.
Container logs are written to packages/evm-wallet-experiment/logs/. Check the service(s) relevant to the failing test mode first:
tail -150 packages/evm-wallet-experiment/logs/<service>.logService log files:
evm.log — Anvil chain (check for on-chain errors)kernel-home-bundler-7702.log, kernel-away-bundler-7702.logkernel-home-bundler-hybrid.log, kernel-away-bundler-hybrid.logkernel-home-peer-relay.log, kernel-away-peer-relay.logStart with the pair(s) involved in the failing test, then evm.log for on-chain issues.
3d5aea9
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.