make level4 runs the level 3 and level 4 scenarios of the pipeline suite and the invariants into evidence/level4.json. New scenarios: worker_limits (a 40 Mpx render under a 0.5 s timeout and a 200 MiB address space fails with processing_failed while the worker keeps running, then succeeds with the default limits under the container limit), retry_backoff_jitter (delays from the job journal stay within [d/2, d] and differ) and failed_retention (failed staging is kept, removed after the retention, then replay answers expired). The stalled holder must be fenced and the republished copy must be a no-op. The faults override passes the stall, render limits and retention through; the admin CLI is python -m messenger.admin. make failed, make replay ID=... and make dlq are the operator entry points; the lab 4 target becomes lab4-level4. CI runs level4 instead of level3. The registry prints ISO timestamps. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
19 lines
704 B
YAML
19 lines
704 B
YAML
services:
|
|
relay:
|
|
restart: "no"
|
|
environment:
|
|
FAULT_POINT: ${RELAY_FAULT_POINT:-}
|
|
OUTBOX_POLL_SECONDS: "0.5"
|
|
SWEEP_INTERVAL_SECONDS: "1"
|
|
STAGING_RETENTION_SECONDS: ${FAULT_STAGING_RETENTION_SECONDS:-${STAGING_RETENTION_SECONDS:-86400}}
|
|
|
|
worker:
|
|
restart: "no"
|
|
environment:
|
|
FAULT_POINT: ${WORKER_FAULT_POINT:-}
|
|
FAULT_STALL_SECONDS: ${FAULT_STALL_SECONDS:-15}
|
|
JOB_TIMEOUT_SECONDS: ${FAULT_JOB_TIMEOUT_SECONDS:-5}
|
|
JOB_BACKOFF_BASE_SECONDS: ${FAULT_BACKOFF_BASE_SECONDS:-1}
|
|
RENDER_TIMEOUT_SECONDS: ${FAULT_RENDER_TIMEOUT_SECONDS:-${RENDER_TIMEOUT_SECONDS:-30}}
|
|
RENDER_MEMORY_MB: ${FAULT_RENDER_MEMORY_MB:-${RENDER_MEMORY_MB:-448}}
|