You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
| `post_test_rpc_calls` | []object | - | Arbitrary RPC calls to execute after each test step (see [Post-Test RPC Calls](#post-test-rpc-calls)) |
@@ -666,6 +667,26 @@ The value is a Go duration string (e.g., `30s`, `1m`, `500ms`). If not set, no a
666
667
- When you observe `SYNCING` responses from Engine API calls despite the RPC being available
667
668
- When starting from pre-populated data directories where clients may need time to validate state
668
669
670
+
##### Run Timeout
671
+
672
+
The `run_timeout` option sets a maximum duration for the test execution phase of a run. If the timeout is exceeded, the run is cancelled with a `timed_out` status. Partial results collected before the timeout are still written and published.
673
+
674
+
```yaml
675
+
runner:
676
+
client:
677
+
config:
678
+
run_timeout: 2h
679
+
```
680
+
681
+
The value is a Go duration string (e.g., `30m`, `1h`, `2h30m`). If not set, no timeout is applied.
682
+
683
+
The timeout covers only the test execution phase — container setup, image pulling, and RPC readiness checks are not included.
684
+
685
+
**When to use:**
686
+
- When running large test suites that may hang or take unexpectedly long
687
+
- When you want to enforce a maximum wall-clock time for benchmark runs
688
+
- When running in CI/CD environments with time constraints
689
+
669
690
##### Retry New Payloads Syncing State
670
691
671
692
When `engine_newPayload` returns a `SYNCING` status, it indicates the client hasn't fully processed the parent block yet. The `retry_new_payloads_syncing_state` option configures automatic retries with exponential backoff.
@@ -833,6 +854,7 @@ runner:
833
854
| `rollback_strategy` | string | No | From `runner.client.config` | Instance-specific rollback strategy |
834
855
| `checkpoint_restore_strategy_options` | object | No | From `runner.client.config` | Instance-specific checkpoint-restore strategy options (replaces global) |
835
856
| `wait_after_rpc_ready` | string | No | From `runner.client.config` | Instance-specific RPC ready wait duration |
857
+
| `run_timeout` | string | No | From `runner.client.config` | Instance-specific run timeout duration |
836
858
| `retry_new_payloads_syncing_state` | object | No | From `runner.client.config` | Instance-specific retry config for SYNCING responses |
837
859
| `resource_limits` | object | No | From `runner.client.config` | Instance-specific resource limits |
838
860
| `post_test_rpc_calls` | []object | No | From `runner.client.config` | Instance-specific post-test RPC calls (replaces global) |
0 commit comments