vfs.unit.test.ts's 'Performance > should handle many files efficiently' (100 writes + readdir, 5.5s write budget) is a wall-clock flake: 121ms alone, 16.5s under the gate's sibling-file contention — the code never caused it. Same pattern already used for storage-batch-operations.test.ts's batch-vs-individual timing case: ctx.skip(!process.env.BRAINY_PERF_LANE, reason) inside the test, and the file added to vitest.perf.config.ts's include list (it stays in the unit gate's *.unit.test.ts match too, so every other test in the file keeps running there). |
||
|---|---|---|
| .. | ||
| tsconfig.typecheck.json | ||
| vitest.integration.config.ts | ||
| vitest.perf.config.ts | ||
| vitest.semantic.config.ts | ||
| vitest.unit.config.ts | ||