exec-timeout-cap
Run time and output are capped
shipped
The sections below are generated from the CLI (methodology 0.3-draft, CLI 0.3.0); the same text is printed by sealmark explain exec-timeout-cap.
- pack
execopt-in pack- weight
- scored
- scope
- server (time and output limits on started programs)
- decided by
- processresponse
- since
- 0.2-draft (methodology 0.3-draft)
- config keys
activechecks.exec-timeout-cap.enabledchecks.exec-timeout-cap.severitytimeout_probe_sec
Probes
sleepprogram sm-sleep for timeout_probe_sec + 20 seconds; it must return within timeout_probe_sec + 8 s and the program must be gonespewprogram sm-spew writes 64 MiB; the reply must be at most 16 MiB or say it was truncated
Settings and thresholds
Every check also takes checks.exec-timeout-cap.enabled and checks.exec-timeout-cap.severity; they are described once in the configuration reference.
| Threshold | Default | Set with | Standard |
|---|---|---|---|
timeout_probe_sec | 10 | timeout_probe_sec | locked |
| Key | Default | Standard | Meaning |
|---|---|---|---|
active | false | not locked | Allow the exec pack and active custom probes to run harness-owned programs. Only the --active flag can set it; files and environment cannot. |
timeout_probe_sec | 10 | locked | Seconds the cap and timeout probes wait before a call counts as running too long (flag --timeout-probe). |
How the verdict is established
- Scoring. scored: pass = 1 point, part = 0.5, fail = 0. A fail lowers the pack's percentage but never caps the letter.
What to fix
Kill programs that run longer than a limit and truncate their output at a byte cap (a timeout under timeout_probe_sec + 8 s and output under 16 MiB).
False positives
A server whose limits are above the probe sizes (more than timeout_probe_sec + 8 s, more than 16 MiB) fails by design of the thresholds.
False negatives
Memory and CPU use are not measured; a reply that is cut by the transport is reported as a failure, not as a cap.