48da420414
Delete unresolved quarantined flaky tests under the deletion ratchet while preserving newer active quarantines. - Remove four flaky test files that were not rescued before the ratchet follow-up. - Drop their matching Vitest excludes and quarantine ledger entries. - Preserve later sync, work-bridge, and core quarantine records from main. Files changed: .../src/__tests__/github-tracking-hook.test.ts | 592 --------------------- packages/dashboard/vitest.config.ts | 8 +- .../src/__tests__/cli-agent-executor.test.ts | 404 -------------- packages/engine/vitest.config.ts | 5 +- .../src/__tests__/orchestrator-flow.test.ts | 156 ------ .../src/__tests__/skill-wiring.test.ts | 101 ---- .../vitest.config.ts | 6 +- scripts/lib/test-quarantine.json | 20 - 8 files changed, 13 insertions(+), 1279 deletions(-) Fusion-Task-Id: FN-6593 Fusion-Task-Lineage: 1165ba24-894a-4cc9-b678-50ae1625ba6b
26 lines
2.7 KiB
JSON
26 lines
2.7 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": "plugins/fusion-plugin-compound-engineering/src/__tests__/sync.test.ts",
|
|
"reason": "CE broad package verification under NODE_ENV=production fix hit a 10000ms beforeEach hook timeout only in the full @fusion-plugin-examples/compound-engineering lane, while an immediate isolated compound-engineering-node run of sync.test.ts passed in 15.43s. Quarantined per deletion-ratchet policy without hookTimeout increases, retries, or assertion loosening.",
|
|
"quarantinedAt": "2026-06-17"
|
|
},
|
|
{
|
|
"file": "plugins/fusion-plugin-compound-engineering/src/__tests__/work-bridge.test.ts",
|
|
"reason": "CE broad package verification under NODE_ENV=production fix hit a 10000ms beforeEach hook timeout only in the full @fusion-plugin-examples/compound-engineering lane, while an immediate isolated compound-engineering-node run of work-bridge.test.ts passed in 10.96s. Quarantined per deletion-ratchet policy without hookTimeout increases, retries, or assertion loosening.",
|
|
"quarantinedAt": "2026-06-17"
|
|
},
|
|
{
|
|
"file": "packages/core/src/__tests__/task-list-format.test.ts",
|
|
"reason": "FN-6596 verification: pnpm test failed in the broad changed-package @fusion/core lane with a beforeEach hook timeout in task-list-format after the merge gate had passed; immediate isolated rerun of the file passed. Quarantined as a suite-load timeout flake without timeout bumps, retries, or assertion loosening.",
|
|
"quarantinedAt": "2026-06-17"
|
|
},
|
|
{
|
|
"file": "packages/core/src/__tests__/test-project.test.ts",
|
|
"reason": "FN-6596 verification: pnpm test failed in the broad changed-package @fusion/core lane with a test timeout in test-project after the merge gate had passed; immediate isolated rerun of the file passed. Quarantined as a suite-load timeout flake without timeout bumps, retries, or assertion loosening.",
|
|
"quarantinedAt": "2026-06-17"
|
|
}
|
|
]
|
|
}
|