53ab22449f
Fix the chat-manager race so the rescued dashboard test can run reliably again. - wait for the first hanging prompt to be created before asserting generation-slot state in the chat-manager isolation test - remove the dashboard chat-manager test from Vitest excludes so it runs in both backfill and default dashboard API projects - clear the chat-manager entry from the flaky-test quarantine ledger after rescuing the test Files changed: packages/dashboard/src/__tests__/chat-manager.test.ts | 16 +++++++++++----- packages/dashboard/vitest.config.ts | 3 +-- scripts/lib/test-quarantine.json | 8 +------- 3 files changed, 13 insertions(+), 14 deletions(-) Fusion-Task-Id: FN-6017 Fusion-Task-Lineage: 5e3bd9ad-3502-4956-bab2-fa7b36f8bcab
5 lines
878 B
JSON
5 lines
878 B
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": []
|
|
}
|