test: cap turbo concurrency so suites stop timing out

Turbo defaults to ten concurrent tasks and each vitest sizes its pool to the
core count, so a ten-core machine ran roughly a hundred workers and a 1.6s test
blew its 15s budget. Different suites failed on every run. At concurrency four
the whole repo passed five runs straight with no wall-clock cost.
This commit is contained in:
Amruth Pillai
2026-08-17 22:19:52 +02:00
parent bfdd29f941
commit ac062bbcbd
+4 -4
View File
@@ -33,13 +33,13 @@
"knip": "knip",
"start": "node apps/server/dist/index.mjs",
"typecheck": "turbo run typecheck",
"test": "turbo run test",
"test:coverage": "turbo run test:coverage",
"test:ci": "turbo run test:ci",
"test": "turbo run test --concurrency=4",
"test:coverage": "turbo run test:coverage --concurrency=4",
"test:ci": "turbo run test:ci --concurrency=4",
"test:e2e": "playwright test",
"test:e2e:ui": "playwright test --ui",
"test:e2e:ci": "playwright test",
"test:agent": "turbo run test:agent"
"test:agent": "turbo run test:agent --concurrency=4"
},
"devDependencies": {
"@biomejs/biome": "^2.5.7",