Files
fusion/scripts/lib/test-quarantine.json
gsxdsm c0d78f19c5 FN-6795: update quarantine ledger after rescue triage
Refresh the test quarantine records after loaded-lane rescue verification.

- document the FN-6795 CLI and core quarantine triage outcomes
- rescue passing core and CLI test files by removing their ledger/config excludes
- retain CLI package-lane-only timeout quarantines and add the newly observed bin test flake

Files changed:
 docs/testing.md                  |  4 ++++
 packages/cli/vitest.config.ts    | 10 +++++++---
 packages/core/vitest.config.ts   |  4 +++-
 scripts/lib/test-quarantine.json | 25 +++++--------------------
 4 files changed, 19 insertions(+), 24 deletions(-)

Fusion-Task-Id: FN-6795
Fusion-Task-Lineage: b4460fc7-848f-4d54-89b4-cfd4d4533d57
2026-06-20 10:28:25 -07:00

21 lines
2.3 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/cli/src/__tests__/bin.test.ts",
"reason": "FN-6795 final @runfusion/fusion package verification observed `launches dashboard when no args are provided` time out at the existing 15s budget only under the full package lane; a targeted rerun with the failing CLI files passed, so quarantine this newly observed suite-load flake on sight instead of widening timeouts or worker budgets.",
"quarantinedAt": "2026-06-20"
},
{
"file": "packages/cli/src/__tests__/extension-task-tools.test.ts",
"reason": "FN-6795 loaded @runfusion/fusion package verification after attempted rescue still timed out both canonical-root task-tool cases only under the full package lane while the targeted rerun with bin/extension-task/extension passed; retain under the original 2026-06-19 deletion ratchet instead of widening the 5s test timeout, adding retries, or changing workers.",
"quarantinedAt": "2026-06-19"
},
{
"file": "packages/cli/src/__tests__/extension.test.ts",
"reason": "FN-6795 loaded @runfusion/fusion package verification after attempted rescue still timed out the built-dist-barrel fn_task_list case only under the full package lane while the targeted rerun with bin/extension-task/extension passed; retain under the original 2026-06-19 deletion ratchet instead of widening the 5s test timeout or weakening assertions.",
"quarantinedAt": "2026-06-19"
}
]
}