5a351b2454
Full-suite repair, mechanical cluster: the wave-18 executor peel (#3317) moved the audited child-spawn bound to executor/create-spawn-agent-tool.ts, the admission-reason unification moved the binding-gate discriminator into concurrency/concurrency.ts, and the FN-9059-era merge-claim and direct workflow-continuation defers read the shared ceiling through resolveActiveTaskCapacityLimit (OFF-mode aware) — all audited with reasons, none is a new raw gate. Core's vitest config now aliases the @fusion/core/mcp-builtin-servers subpath before the bare alias (mirroring engine's config) so core PG tests that exercise engine's mcp-resolution resolve it from source. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
66 lines
3.1 KiB
TypeScript
66 lines
3.1 KiB
TypeScript
import { defineConfig } from "vitest/config";
|
|
import { resolve } from "node:path";
|
|
import { computeMaxWorkers } from "./src/__test-utils__/vitest-workers";
|
|
|
|
const maxWorkers = computeMaxWorkers();
|
|
|
|
/*
|
|
FNXC:CoreTestInventory 2026-07-13-22:38:
|
|
Core test exclusions must exactly mirror the dated quarantine ledger. The PostgreSQL cutover removed the SQLite runtime and the expired 2026-07-10 exclusions no longer have ledger authority; keep this list empty and preserve behavior through active PostgreSQL counterparts.
|
|
|
|
FNXC:FullSuiteBookkeeping 2026-08-09-03:49:
|
|
All 14 core entries from the 2026-08-05 full-suite quarantine wave (run 30982276306) were deleted under the deletion ratchet after operator directive. These tested pre-refactor APIs/mock shapes (layer.db.select, peeled workflow IR resolvers, stale serialization literals) that no longer exist post-cutover. Array intentionally empty.
|
|
*/
|
|
const quarantinedCoreTests: string[] = [];
|
|
|
|
export default defineConfig({
|
|
resolve: {
|
|
alias: {
|
|
/*
|
|
FNXC:MemoryMcp 2026-08-15-22:05:
|
|
Core PG tests exercise engine source (e.g. command-center activity via engine's
|
|
mcp-resolution.ts), which imports the Node-only `@fusion/core/mcp-builtin-servers` subpath.
|
|
Without this entry the bare `@fusion/core` alias below prefix-rewrites the subpath into
|
|
`src/index.ts/mcp-builtin-servers` and resolution fails. Mirrors engine/vitest.config.ts;
|
|
subpath entries must precede the bare alias.
|
|
*/
|
|
"@fusion/core/mcp-builtin-servers": resolve(__dirname, "./src/config/mcp-builtin-servers.ts"),
|
|
"@fusion/core": resolve(__dirname, "./src/index.ts"),
|
|
"@fusion/test-utils": resolve(__dirname, "./src/__test-utils__/workspace.ts"),
|
|
"@fusion/plugin-sdk": resolve(__dirname, "../plugin-sdk/src/index.ts"),
|
|
},
|
|
},
|
|
test: {
|
|
include: ["src/**/*.test.ts"],
|
|
exclude: quarantinedCoreTests,
|
|
setupFiles: [
|
|
"./src/__test-utils__/vitest-setup.ts",
|
|
],
|
|
globalSetup: ["./src/__test-utils__/vitest-teardown.ts"],
|
|
// Must stay "forks". Two thread-unsafe patterns block migration to "threads":
|
|
//
|
|
// 1. vitest-setup.ts:123 — `process.chdir(workerTempDir)` is gated by
|
|
// `isMainThread`, which is `false` in worker_threads, so each thread
|
|
// worker never gets its isolated cwd. Tests that rely on cwd being a
|
|
// disposable temp dir would silently operate in the repo root.
|
|
//
|
|
// 2. Some suites rely on fork-level process/env isolation for setup side effects,
|
|
// and cannot safely share mutable process state under worker_threads.
|
|
pool: "forks",
|
|
maxWorkers,
|
|
minWorkers: 1,
|
|
fileParallelism: true,
|
|
// Core runs a large SQLite-heavy suite while other workspace packages test concurrently.
|
|
// Use a slightly higher timeout to reduce nondeterministic slow-machine flakes.
|
|
testTimeout: 15_000,
|
|
hookTimeout: 15_000,
|
|
coverage: {
|
|
enabled: false,
|
|
reporter: ["text", "html", "json"],
|
|
reportsDirectory: "./coverage",
|
|
include: ["src/**/*.ts"],
|
|
exclude: ["**/*.test.ts", "**/*.d.ts", "dist/**"],
|
|
},
|
|
},
|
|
});
|