1a565a368b
Rescue the WorkflowNodeEditor quarantine by making duplicate merge seam detection reliable during initial canvas load. - Derive fragment seam conflicts from the loaded workflow IR until React Flow nodes materialize. - Treat IR merge nodes as merge seams so duplicate merge fragments are rejected consistently. - Cover desktop and mobile duplicate merge fragment insertion paths and remove the test from quarantine. - Document the FN-6744 rescue evidence and deletion-ratchet update. Files changed: docs/testing.md | 6 +++- .../app/components/WorkflowNodeEditor.tsx | 11 +++++-- .../__tests__/WorkflowNodeEditor.test.tsx | 34 ++++++++++++++++------ .../app/components/workflow-flow-mapping.ts | 10 +++++++ packages/dashboard/vitest.config.ts | 8 +++-- scripts/lib/test-quarantine.json | 5 ---- 6 files changed, 54 insertions(+), 20 deletions(-) Fusion-Task-Id: FN-6744 Fusion-Task-Lineage: 0f5b167a-8efc-4458-ac9d-e719320b751f
36 lines
3.5 KiB
JSON
36 lines
3.5 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/core/src/__tests__/store-concurrent-writes.test.ts",
|
|
"reason": "FN-6741 merge verification observed store-concurrent-writes fail again only under the broad @fusion/core lane with SQLite BEGIN IMMEDIATE lock exhaustion after the other same-day core quarantine entries stayed loaded; re-quarantine this suite-load lock flake instead of widening SQLite lock-recovery timing, adding retries, or weakening concurrent-write assertions.",
|
|
"quarantinedAt": "2026-06-19"
|
|
},
|
|
{
|
|
"file": "packages/cli/src/__tests__/extension-goal-tools.test.ts",
|
|
"reason": "FN-6705 local workspace `pnpm test` observed extension-goal-tools timing out and leaking state only in the broad changed-package CLI lane; immediate targeted rerun with the CLI failure batch passed this file, so quarantine the suite-load flake instead of widening the 5s test timeout or weakening goal-list assertions.",
|
|
"quarantinedAt": "2026-06-19"
|
|
},
|
|
{
|
|
"file": "packages/cli/src/__tests__/extension-mission-goal-tools.test.ts",
|
|
"reason": "FN-6705 local workspace `pnpm test` observed extension-mission-goal-tools timing out and leaving ENOTEMPTY cleanup only in the broad changed-package CLI lane; immediate targeted rerun with the CLI failure batch passed this file, so quarantine the suite-load flake instead of timeout/retry appeasement.",
|
|
"quarantinedAt": "2026-06-19"
|
|
},
|
|
{
|
|
"file": "packages/cli/src/__tests__/extension-task-tools.test.ts",
|
|
"reason": "FN-6705 verification observed extension-task-tools timeout under both the broad changed-package CLI lane and a direct rerun while unrelated task surfaces still passed; quarantine the load-sensitive repo-root integration file under the deletion ratchet instead of raising testTimeout.",
|
|
"quarantinedAt": "2026-06-19"
|
|
},
|
|
{
|
|
"file": "packages/cli/src/__tests__/extension.test.ts",
|
|
"reason": "FN-6705 local workspace `pnpm test` observed extension.test fn_task_list cases time out and hit ENOTEMPTY cleanup only in the broad changed-package CLI lane; immediate targeted rerun with the CLI failure batch passed this file, so quarantine the suite-load flake instead of appeasing it.",
|
|
"quarantinedAt": "2026-06-19"
|
|
},
|
|
{
|
|
"file": "packages/cli/src/__tests__/research-extension-tools.test.ts",
|
|
"reason": "FN-6705 local workspace `pnpm test` observed research-extension-tools timing/assertion drift only in the broad changed-package CLI lane; immediate targeted rerun with the CLI failure batch passed this file, so quarantine the suite-load flake instead of loosening assertions or adding retries.",
|
|
"quarantinedAt": "2026-06-19"
|
|
}
|
|
]
|
|
}
|