5ab4a5961c
Restore quarantined scheduler/reliability coverage while preserving override column-agent model selection. - remove rescued engine and CLI tests from quarantine configs and the ledger - add scheduler fake updateSettings coverage so heartbeat writes do not skew call-count assertions - preserve override column-agent runtime models during initial execution and mid-flight task edits - update the stale user-configured command guard registry and add a patch changeset Files changed: .changeset/fn-7119-column-agent-model.md | 7 +++ docs/testing.md | 2 + packages/cli/vitest.config.ts | 6 +- .../executor-column-agent-principal.test.ts | 34 +++++++++- .../lease-recovery-central-claim.test.ts | 5 ++ .../owning-node-unavailable-interactions.test.ts | 5 ++ .../todo-inprogress-flapping.test.ts | 5 ++ .../src/__tests__/restart.integration.test.ts | 8 +++ .../__tests__/scheduler-ephemeral-toggle.test.ts | 5 ++ .../scheduler-node-unreachable-audit.test.ts | 5 ++ .../__tests__/scheduler-overlap-starvation.test.ts | 5 ++ .../user-configured-command-no-execsync.test.ts | 12 +--- packages/engine/src/executor.ts | 18 ++++-- packages/engine/vitest.config.ts | 26 +++----- scripts/lib/test-quarantine.json | 73 +--------------------- 15 files changed, 106 insertions(+), 110 deletions(-) Fusion-Task-Id: FN-7119 Fusion-Task-Lineage: 7dc033c8-29d1-4c0e-bfc1-b0ff0d325f43 Co-authored-by: Fusion (runfusion.ai) <noreply@runfusion.ai>
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": []
|
|
}
|