chopratejas 2ae88a6874 fix(tests): widen wrap-e2e openclaw startup timeout from 5s to 30s ... The wrap-e2e harness passed `--startup-timeout-ms 5000` to `headroom wrap openclaw`, leaving zero slack for the openclaw plugin's auto-start launcher to bring up the headroom proxy before the 5s health-check deadline. On a busy CI runner, cold Python import of `headroom.cli` plus pyo3 dlopen plus FastAPI app boot routinely lands in the 4–8s range, so this was always a coin-flip. Evidence: run 25897154424 failed on main with the exact code that passed pre-merge on PR #474's docker-wrap-e2e check (run 25897085244). Both logs show identical openclaw "Config warnings" output — that's normal noise, not the cause. The differentiating line is `[plugins] Headroom proxy started and reachable` (pass) vs `[plugins] Headroom proxy unavailable: health check failed` (fail). 30s matches what other wrap-e2e callers already use as a working margin for the headroom proxy boot path; the runtime default for `headroom wrap openclaw --startup-timeout-ms` is 20s.		2026-05-14 20:00:29 -07:00
..
_lib	test(init): extend Docker e2e with bare/shim/per-subcommand cases	2026-04-23 16:12:27 -05:00
init	test(init-e2e): expect mcp add in seq_claude_local install sequence	2026-05-08 17:38:34 -07:00
wrap	fix(tests): widen wrap-e2e openclaw startup timeout from 5s to 30s	2026-05-14 20:00:29 -07:00
__init__.py	test(init): extend Docker e2e with bare/shim/per-subcommand cases	2026-04-23 16:12:27 -05:00
docker-native-install.sh	test(e2e): assert HEADROOM_WORKSPACE_DIR / HEADROOM_CONFIG_DIR reach container at runtime	2026-04-16 19:59:56 -05:00