Yunfei He
a4116ba08f
The fourth CI run failed broadly: ~15 timing-sensitive tests (throttle, flush, resize clear-counts, rapid-input ordering) failed under sequence.concurrent on the 4-core ubuntu runner. These assert render/commit counts driven by the ~32ms commit throttle; in-file concurrency starves them of wall-clock when many share few cores. It passed locally only because dev machines have more cores — the classic "works on my 12-core mac" trap. Remove sequence.concurrent from both the main and PTY configs; keep fileParallelism (pool: forks), which is the proven, stable win (PTY suite still ~3x faster than serial). The it.sequential/describe.sequential markers and context-local expect become harmless no-ops under serial in-file execution. Verified cold (no dist): vp run ci exits 0, 0 lint warnings, all tests pass.
19 lines
739 B
TypeScript
19 lines
739 B
TypeScript
import { defineConfig } from "vite-plus";
|
|
import vueJsx from "@vitejs/plugin-vue-jsx";
|
|
|
|
export default defineConfig({
|
|
plugins: [vueJsx()],
|
|
test: {
|
|
// chalk disables color in non-TTY envs; force it on so ANSI style bugs don't hide from tests
|
|
env: { FORCE_COLOR: "3" },
|
|
// Files parallelize, but tests within a file run serially: many assert
|
|
// timing-sensitive render/commit/flush counts that destabilize under
|
|
// in-file concurrency on a constrained (4-core) CI runner.
|
|
// PTY tests run separately via vitest.pty.config.ts (they need node-pty's forks pool and a longer timeout)
|
|
exclude: ["integration/pty/**", "node_modules/**"],
|
|
},
|
|
lint: {
|
|
ignorePatterns: ["integration/pty/fixtures/**"],
|
|
},
|
|
});
|