beb8ae67db
Classify the suite-only failures by actual PostgreSQL dependency and preserve unresolved evidence for follow-up. - Record non-reproduction results and assign PostgreSQL investigations to focused follow-up tasks. - Quarantine the independent in-memory plugin runner test under the deletion ratchet. - Document evidence requirements for future PostgreSQL flake diagnosis. Files changed: .../suite-only-flakes-observed-register.md | 32 ++++++++++++++++++++-- docs/testing.md | 4 +++ packages/engine/vitest.config.ts | 10 +++++++ scripts/lib/test-quarantine.json | 8 +++++- 4 files changed, 51 insertions(+), 3 deletions(-) Fusion-Task-Id: FN-9125 Fusion-Task-Lineage: 1dc80163-a0dc-4241-bab1-75a2cafb9abe Co-authored-by: Fusion (runfusion.ai) <noreply@runfusion.ai>
11 lines
1.5 KiB
JSON
11 lines
1.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 is the enforcement.",
|
|
"entries": [
|
|
{
|
|
"file": "packages/engine/src/__tests__/plugin-runner.test.ts",
|
|
"reason": "FN-9125: first-sighting register entry 3; failure evidence https://github.com/Runfusion/Fusion/pull/2799#issuecomment-5134921769 captures seven loaded-engine failures on the PR #2799 merged-with-main tree, but only `PluginRunner > task lifecycle hooks > should invoke onTaskCompleted when the complete lane is RENAMED` survived because the original dot output was truncated. FN-9125 confirmed the file is in-memory/mocked and not PostgreSQL-backed; no current structural failure was reproducible. Quarantined under the deletion ratchet rather than weakening lifecycle assertions.",
|
|
"quarantinedAt": "2026-08-16"
|
|
}
|
|
]
|
|
}
|