Give all_spec_routes_are_routable a 30s timeout that actually applies

The test has had a dedicated override since it was first flagged as slow,
but it sat below the package-wide `package(fabro-server)` entry. Nextest
resolves each setting from the first matching override, so the broader
filter won and the narrower one was dead config.

The effective timeout was therefore the package default, 5s x 4 = 20s. The
test runs 15-19s and tripped that under full-workspace load.

Move the override above the package entry and set 10s x 3, so it is both
reachable and a 30s kill. Confirmed by the SLOW marker moving from >5s to
>10s.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
This commit is contained in:
Bryan Helmkamp 2026-07-27 18:26:35 -04:00
parent 24b0576ffe
commit 7950441bee
No known key found for this signature in database

View file

@ -7,14 +7,17 @@ leak-timeout = "500ms"
filter = "package(fabro-cli)"
slow-timeout = { period = "6s", terminate-after = 4 }
# Must stay above the package-wide fabro-server override: nextest resolves
# each setting from the first matching override, so a narrower filter
# placed after a broader one never applies.
[[profile.default.overrides]]
filter = "package(fabro-server) & test(all_spec_routes_are_routable)"
slow-timeout = { period = "10s", terminate-after = 3 }
[[profile.default.overrides]]
filter = "package(fabro-server)"
slow-timeout = { period = "5s", terminate-after = 4 }
[[profile.default.overrides]]
filter = "package(fabro-server) & test(all_spec_routes_are_routable)"
slow-timeout = { period = "15s", terminate-after = 4 }
[[profile.default.overrides]]
filter = "package(fabro-workflow)"
slow-timeout = { period = "2s", terminate-after = 3 }