1020b3f83f
Restore the compound-engineering broad lane tests after the timeout could not be reproduced on the stabilized shared test infrastructure. - Re-enable the compound-engineering sync and work-bridge tests by clearing their Vitest quarantine excludes. - Remove the stale quarantine ledger entries now that the broad package lane stayed stable under verification. Files changed: plugins/fusion-plugin-compound-engineering/vitest.config.ts | 10 ++++------ scripts/lib/test-quarantine.json | 13 +------------ 2 files changed, 5 insertions(+), 18 deletions(-) Fusion-Task-Id: FN-6606 Fusion-Task-Lineage: f357c626-c181-44a7-a463-c53644566ca1
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": []
|
|
}
|