Bryan Helmkamp 87fd6d5cd4 Give Daytona live tests a slow-timeout that fits a sandbox and a Playwright install ... The e2e nextest profile flags a test as slow after 10s and kills it after three periods, 30s in all. A Daytona live test creates a remote sandbox, installs tools in it, and waits for the provider; the Playwright MCP test also fetches a 114 MiB browser and completes an MCP handshake through the preview URL. A measured live run took 40.6s, so the documented `--profile e2e --run-ignored only` command killed it before it could report its own result. Add an e2e override for every `daytona_` test that raises the slow period to 60s and the kill to 20 periods, so a slow provider has room while a hung test still ends. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>		2026-09-14 09:40:28 -06:00
..
nextest.toml	Give Daytona live tests a slow-timeout that fits a sandbox and a Playwright install	2026-09-14 09:40:28 -06:00