3e69d3990d
Ensure AI merge cleanup only reaps stale, inactive temp worktrees. - Register live AI merge clean-room paths in the active session registry while merges run. - Add a minimum temp-worktree reap age and conservative lookup-error handling to sweep and prune paths. - Expand cleanup tests and release the repaired AI merge cleanup test from quarantine. Files changed: docs/architecture.md | 2 +- .../engine/src/__tests__/merger-ai-cleanup.test.ts | 38 ++++++++++++++-- .../__tests__/self-healing-tempdir-sweep.test.ts | 52 +++++++++++++++++++--- packages/engine/src/active-session-registry.ts | 2 +- packages/engine/src/merger-ai.ts | 29 +++++++++++- packages/engine/src/self-healing.ts | 28 +++++++++--- packages/engine/vitest.config.ts | 1 - scripts/lib/test-quarantine.json | 5 --- 8 files changed, 132 insertions(+), 25 deletions(-) Fusion-Task-Id: FN-6244 Fusion-Task-Lineage: 5c8ced12-d38f-4e45-9ea0-119b3236a2cb
21 lines
2.1 KiB
JSON
21 lines
2.1 KiB
JSON
{
|
|
"$comment": "Flaky-test quarantine ledger (deletion ratchet — see AGENTS.md 'Flaky tests: quarantine on sight' and docs/testing.md 'Quarantine ledger and the deletion ratchet'). A test observed failing without a corresponding real bug is quarantined ON SIGHT: add an entry here AND a matching one-line `exclude` entry in that package's vitest config, in the same commit. Every entry needs a non-empty `reason` (link the failing run) and a `quarantinedAt` date — the entry expires 14 days later, at which point the test file is DELETED unless someone rescues it with evidence it catches real regressions plus a root-cause fix (never appeasement). There is deliberately no loader module and no automation around this file: it is a dated record, the vitest config exclude is the mechanism, and the sweep is policy executed by whoever touches the suite.",
|
|
"entries": [
|
|
{
|
|
"file": "packages/engine/src/__tests__/project-engine-manager.test.ts",
|
|
"reason": "Flake: setInterval-driven reconciliation races with vitest fake-timer contention under full reliability-suite load. Test passes standalone (~46ms) but times out (30s) when reliability-pool files are co-resident. FN-6206.",
|
|
"quarantinedAt": "2026-06-10"
|
|
},
|
|
{
|
|
"file": "packages/engine/src/__tests__/merger-file-scope-invariant.test.ts",
|
|
"reason": "Flake: vi.mock('node:child_process') occasionally doesn't take under workspace-concurrent runs, letting real git binary leak and report staged files unrelated to test scope (trips FileScopeViolationError). Same logic covered by real-git fixture tests in reliability-interactions/workflow-and-file-scope. FN-6206.",
|
|
"quarantinedAt": "2026-06-10"
|
|
},
|
|
{
|
|
"file": "packages/engine/src/__tests__/self-healing-already-merged.real-git.test.ts",
|
|
"reason": "Flake observed during FN-6226 verification: full `pnpm --filter @fusion/engine test` expected two run-audit events but saw four after unrelated real-git/self-healing cleanup activity. The failure is outside fast-mode workflow changes and indicates suite-order/temp-state sensitivity.",
|
|
"quarantinedAt": "2026-06-10"
|
|
}
|
|
]
|
|
}
|