Fix idle watchdog timeout inheritance #3
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "codex/idle-watchdog-env"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Summary\n- let the idle watchdog inherit IDLE_TIMEOUT_S from the container/pod environment instead of hardcoding 600s in supervisord\n- add a smoke assertion that IDLE_TIMEOUT_S=999999 reaches the watchdog at runtime\n\n## Verification\n- bash -n tests/smoke/container-boot.sh infra/lifecycle/idle-watchdog.sh infra/lifecycle/cold-start.sh\n- python3 configparser check that program:idle-watchdog no longer overrides IDLE_TIMEOUT_S\n- git diff --check\n\n## Operator note\nThe live chromeless-browserless pod is currently restarting cb-chromium around the 10-minute idle threshold even though the deployment sets IDLE_TIMEOUT_S=999999. This PR fixes that packaging/runtime path; after merge, build a new canonical cr7727-* runtime image and roll chromeless/chromeless-browserless.