Yunfei He
a07fc889c4
With resize rendering now synchronous, no PTY test depends on wall-clock timing, so concurrent execution is safe. Enable sequence.concurrent: true. Each test already spawns its own isolated PTY subprocess (or in-process app) with no shared state. Verified stable: 12/12 runs green under sequence.concurrent with forks capped to 4 (mimicking a 4-core CI runner) — the configuration that reliably flaked before the resize fix. No it.sequential opt-outs are needed.
25 lines
1.1 KiB
TypeScript
25 lines
1.1 KiB
TypeScript
import { defineConfig } from "vite-plus";
|
|
import vueJsx from "@vitejs/plugin-vue-jsx";
|
|
|
|
export default defineConfig({
|
|
plugins: [vueJsx()],
|
|
test: {
|
|
include: ["integration/pty/**/*.test.{ts,tsx}"],
|
|
// node-pty requires child_process.fork(), not worker_threads, so the pool
|
|
// MUST be "forks". Each test spawns its own isolated PTY subprocess (no
|
|
// shared ports/files/global state), so test files parallelize safely across
|
|
// forked workers — ~3x faster than serial (the PTY suite is the CI's
|
|
// wall-clock bottleneck). testTimeout stays generous (15s vs ~2s slowest
|
|
// test) to absorb CPU contention on smaller CI runners.
|
|
pool: "forks",
|
|
fileParallelism: true,
|
|
// Tests run concurrently by default. Each spawns its own isolated PTY
|
|
// subprocess (or in-process app) with no shared state, and rendering is no
|
|
// longer wall-clock-dependent (resize renders synchronously), so exact
|
|
// render-count assertions stay deterministic even under CPU contention.
|
|
sequence: { concurrent: true },
|
|
testTimeout: 15000,
|
|
env: { FORCE_COLOR: "3" },
|
|
},
|
|
});
|