From 87fd6d5cd46b41c01ecf6d8f7296c081ab8fd37d Mon Sep 17 00:00:00 2001 From: Bryan Helmkamp Date: Mon, 14 Sep 2026 09:40:28 -0600 Subject: [PATCH] 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 --- .config/nextest.toml | 9 +++++++++ 1 file changed, 9 insertions(+) diff --git a/.config/nextest.toml b/.config/nextest.toml index c55b0bd0d..aaec8ca9c 100644 --- a/.config/nextest.toml +++ b/.config/nextest.toml @@ -26,6 +26,15 @@ leak-timeout = "500ms" slow-timeout = { period = "10s", terminate-after = 3 } leak-timeout = "500ms" + # Daytona live tests create a remote sandbox, install tools in it (the + # Playwright MCP test fetches a 114 MiB browser), and wait for an MCP + # handshake through the preview URL. The measured run is ~41s, past the + # 30s hard kill above; 20 minutes leaves room for a slow provider without + # letting a hung test run forever. + [[profile.e2e.overrides]] + filter = "test(/daytona_/)" + slow-timeout = { period = "60s", terminate-after = 20 } + [profile.ci] # CI runners are slower and more variable than dev machines; give tests room # before flagging them as hung. CI uses one uniform timeout for every test.