FN-6606: restore CE sync lane coverage
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
This commit is contained in:
@@ -23,13 +23,11 @@ FNXC:CompoundEngineeringTests 2026-06-17-16:20:
|
||||
FN-6593 deletes orchestrator-flow.test.ts and skill-wiring.test.ts under the ratchet because the broad-workflow-only 5000ms timeout could not be tied to a narrow non-appeasement root cause.
|
||||
Keep the ledger entries and excludes removed together; git history remains the archive for this dropped CE orchestrator/skill-wiring coverage.
|
||||
|
||||
FNXC:CompoundEngineeringTests 2026-06-17-17:18:
|
||||
The CE broad package lane still times out in sync/work-bridge hooks under project concurrency while both files pass in isolation. Quarantine the files under the deletion ratchet instead of raising hook timeouts or serializing the whole plugin lane.
|
||||
FNXC:CompoundEngineeringTests 2026-06-17-19:56:
|
||||
FN-6606 re-ran the loaded CE node/package lane with sync.test.ts and work-bridge.test.ts temporarily unexcluded and could not reproduce either the 5000ms test timeout or the later 10000ms hook timeout.
|
||||
The current HEAD's shared test-isolation fixes now keep the broad lane stable, so restore both files to active coverage and clear the stale quarantine in lockstep with scripts/lib/test-quarantine.json.
|
||||
*/
|
||||
const quarantinedCompoundEngineeringTests = [
|
||||
"src/__tests__/sync.test.ts",
|
||||
"src/__tests__/work-bridge.test.ts",
|
||||
];
|
||||
const quarantinedCompoundEngineeringTests = [];
|
||||
const nodeOnlyDashboardTests = [
|
||||
"src/dashboard/__tests__/theme-tokens.test.ts",
|
||||
];
|
||||
|
||||
@@ -1,15 +1,4 @@
|
||||
{
|
||||
"$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": "plugins/fusion-plugin-compound-engineering/src/__tests__/sync.test.ts",
|
||||
"reason": "CE broad package verification under NODE_ENV=production fix hit a 10000ms beforeEach hook timeout only in the full @fusion-plugin-examples/compound-engineering lane, while an immediate isolated compound-engineering-node run of sync.test.ts passed in 15.43s. Quarantined per deletion-ratchet policy without hookTimeout increases, retries, or assertion loosening.",
|
||||
"quarantinedAt": "2026-06-17"
|
||||
},
|
||||
{
|
||||
"file": "plugins/fusion-plugin-compound-engineering/src/__tests__/work-bridge.test.ts",
|
||||
"reason": "CE broad package verification under NODE_ENV=production fix hit a 10000ms beforeEach hook timeout only in the full @fusion-plugin-examples/compound-engineering lane, while an immediate isolated compound-engineering-node run of work-bridge.test.ts passed in 10.96s. Quarantined per deletion-ratchet policy without hookTimeout increases, retries, or assertion loosening.",
|
||||
"quarantinedAt": "2026-06-17"
|
||||
}
|
||||
]
|
||||
"entries": []
|
||||
}
|
||||
|
||||
Reference in New Issue
Block a user