scriptoriumadmin/fabro
1
0
Fork 0
mirror of https://github.com/fabro-sh/fabro.git synced 2026-10-01 02:04:24 +00:00
Code Issues Projects Releases Packages Wiki Activity Actions 3

Give Daytona live tests a slow-timeout that fits a sandbox and a Playwright install

Browse source 
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>
This commit is contained in:
Bryan Helmkamp 2026-09-14 09:40:28 -06:00
parent 15198ca23a
commit 87fd6d5cd4
1 changed files with 9 additions and 0 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

9
.config/nextest.toml
View file

@ -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.