aaltshuler 211b37e6de test(cluster): failpoint tests for crash-mid-apply and state CAS race ... The apply-side coverage the implementation spec's hard gate requires before Phase 4 graph-moving apply: - crash after the payload phase: state.json byte-identical, blobs inert on disk, lock released, no phantom statuses, nothing acknowledged; a plain re-run repairs via skip-if-exists blob reuse. - CAS race: a cfg_callback rewrites state.json at the exact read->write window (the state.lock:false concurrent-writer scenario); apply surfaces state_cas_mismatch, acknowledges nothing, reports the persisted status snapshot, leaves the concurrent writer's state on disk; a re-run converges. CI's failpoints step now runs both the engine and cluster suites. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>		2026-06-10 02:14:06 +03:00
..
src	feat(cluster): failpoint infrastructure mirroring the engine	2026-06-10 02:12:59 +03:00
tests	test(cluster): failpoint tests for crash-mid-apply and state CAS race	2026-06-10 02:14:06 +03:00
Cargo.toml	feat(cluster): failpoint infrastructure mirroring the engine	2026-06-10 02:12:59 +03:00