test(evm): cap child_process.exec in lib.js to surface stalled commands

[wen-coding]

Summary

execCommand in contracts/test/lib.js wraps child_process.exec with no timeout. The Autobahn EVM integration matrix has hit multiple 30‑minute job timeouts where the hardhat process went silent at a test boundary, with the orphan‑process listing at cleanup consistently showing a stalled docker exec ... seid ... child still alive. The job then consumed its entire wall‑clock budget instead of surfacing a useful error.

This caps execCommand with a configurable timeout (default 60s, SIGKILL). On expiry, the rejection includes the offending command so the next occurrence is a 60s actionable error instead of a 30‑minute mystery. Override via EXEC_TIMEOUT_MS for tests that legitimately need longer.

Observed hang pattern (7 occurrences in 3 days)

Date (UTC)	Run	Affected Autobahn matrix job	Branch
05‑28 23:48	26608835541	EVM Interoperability	chore branch
05‑29 00:06	26609440164	EVM Interoperability	chore branch
05‑29 06:00	26620669539	EVM Interoperability	chore branch
05‑29 14:19	26642258916	EVM Interoperability	merge_queue #3506
05‑29 16:22	26648904362	EVM Interoperability	main push
05‑29 16:29	26648905384	EVM Interoperability	merge_queue #3511
05‑31 01:00	26699345153	EVM Module	PR #3525

Each ran for exactly ~30 minutes (job timeout). Investigation of one of the artifacts (26648905384): validators were perfectly healthy (continuing to produce blocks) the whole time, no test‑sender activity reached them during the silence — i.e., the hardhat process was alive but never sent another RPC, consistent with a stalled child process here.

Trade-off

• Healthy docker exec calls in the suite complete in ~100–200ms; 60s is comfortably above the worst observed normal case.
• If a specific test legitimately needs longer (e.g. genesis bootstrap), EXEC_TIMEOUT_MS overrides per-invocation.

Test plan

• CI: full integration matrix passes (60s is well above normal).
• The next time this stall pattern hits, the failing job will report a 60s execCommand timed out … <command> error instead of a 30‑min cancel — that error itself becomes the diagnostic.

🤖 Generated with Claude Code

[cursor]

PR Summary

Low Risk
Test-harness-only change; no production or chain logic, with an env override for legitimately long runs.

Overview
execCommand in contracts/test/lib.js now passes a child_process.exec timeout (default 60s, overridable via EXEC_TIMEOUT_MS) with SIGKILL, so hung docker exec … seid … calls fail fast instead of burning the full CI job budget.

On timeout it rejects with a message that includes the command (truncated past 200 chars). error.killed && !error.code is used so maxBuffer overflows and external kills are not reported as timeouts.

^{Reviewed by Cursor Bugbot for commit 22e2a83. Bugbot is set up for automated code reviews on this repo. Configure here.}

[github-actions]

The latest Buf updates on your PR. Results from workflow Buf / buf (pull_request).

Build	Format	Lint	Breaking	Updated (UTC)
✅ passed	✅ passed	✅ passed	✅ passed	Jun 1, 2026, 7:15 PM

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 58.30%. Comparing base (f8f1af1) to head (22e2a83).

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #3526      +/-   ##
==========================================
- Coverage   59.12%   58.30%   -0.83%     
==========================================
  Files        2213     2140      -73     
  Lines      182774   174338    -8436     
==========================================
- Hits       108072   101649    -6423     
+ Misses      64985    63666    -1319     
+ Partials     9717     9023     -694     

Flag	Coverage Δ
sei-db	70.41% <ø> (ø)
sei-db-state-db	?

Flags with carried forward coverage won't be shown. Click here to find out more.
see 105 files with indirect coverage changes

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[cursor]

Cursor Bugbot has reviewed your changes using default effort and found 1 potential issue.

^{❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.}

^{Reviewed by Cursor Bugbot for commit c1920c4. Configure here.}