A 8d3f848907 fix(e2e): increase openclaw gateway resilience timeout to 60s (#2587) ... GCP e2-micro VMs are slow and throttled. When the openclaw gateway is killed during the resilience test, the lock file is held by the dead process for ~5s. This causes the first systemd restart attempt to fail with "lock timeout after 5000ms", requiring a second restart cycle. Timeline on slow VMs: RestartSec(5) + lock-timeout(5) + RestartSec(5) + boot(5) ≈ 20s. The previous 30s window was too tight — the gateway DID recover but just barely missed the polling window on throttled CPUs. Increasing to 60s gives a comfortable 3x margin for all VM types. Co-authored-by: spawn-qa-bot <qa@openrouter.ai> Co-authored-by: Claude Sonnet 4.6 <noreply@anthropic.com> Co-authored-by: L <6723574+louisgv@users.noreply.github.com>		2026-03-13 13:48:02 -04:00
..
clouds	security: validate base64 output in cloud_exec and soak.sh (defense-in-depth) (#2532)	2026-03-12 09:32:48 -04:00
common.sh	fix(e2e): fix OPENROUTER_API_KEY fallback and sprite env whitelist (#2491)	2026-03-11 03:23:46 -04:00
provision.sh	fix(e2e): add retry-with-backoff for DigitalOcean 422 droplet limit errors (#2520)	2026-03-12 07:49:47 +00:00
soak.sh	feat(qa): telegram soak test on digitalocean + fix bun -e (#2547)	2026-03-12 19:45:18 -04:00
teardown.sh	feat(e2e): multi-cloud test suite with cloud driver pattern (#2004)	2026-02-27 19:28:08 -08:00
verify.sh	fix(e2e): increase openclaw gateway resilience timeout to 60s (#2587)	2026-03-13 13:48:02 -04:00