DeepSeek/deepseek-harness
1
0
Fork 0
mirror of https://github.com/deepseek-ai/deepseek-harness synced 2026-08-15 21:04:50 +00:00
Code Issues Packages Projects Releases Wiki Activity

perf(test): run replay snapshot files in parallel

Browse Source 
The snapshot config serialized all 13 files for every mode, but the
fixture-writing rationale only holds for record (real API quota per
scenario) and refresh (write-back harvests volatile values from
fixtures on disk). Replay — the keyless default and the CI mode — is
read-only with a unique temp dir per scenario subprocess, and the
suite factory already runs replay scenarios concurrently in-file.

Narrow the serialization to non-replay modes: pnpm test:snapshot drops
from ~49s to ~33s wall; record/refresh stay fully serial.
This commit is contained in:
Turtle
2026-07-31 15:46:00 +08:00
parent 3a060c5688
commit ecdcc218b6
1 changed files with 8 additions and 4 deletions
Download Patch File Download Diff File Expand all files Collapse all files

12
vitest.snapshot.config.ts
View File

@@ -55,12 +55,16 @@ export default defineConfig({
'packages/sdk/*/tests/**/*.snapshot.ts',
'packages/ui/tui/tests/**/*.snapshot.ts',
],
// Each test boots a subprocess; give it room and keep the worker file singular. Replay tests
// opt into bounded in-file concurrency, while record/refresh stay serial because they write
// fixtures. The environment knob restores serial replay with value 1 on constrained machines.
// Each test boots a subprocess; give it room. Replay scenarios are
// read-only (unique temp dir and fixture set per subprocess), so replay
// runs the snapshot files in parallel and bounds in-file concurrency with
// the environment knob (value 1 restores serial replay on constrained
// machines). Record and refresh stay fully serial: record spends real API
// quota per scenario, and refresh write-back harvests volatile values from
// fixtures already on disk, so concurrent writers would corrupt goldens.
testTimeout: 120_000,
hookTimeout: 30_000,
fileParallelism: false,
fileParallelism: (process.env.DSH_SNAPSHOT || 'replay') === 'replay',
maxConcurrency: snapshotMaxConcurrency,
},
})