prisma-risk / tsoracle / 26371395704

95%

Build Type

push

github

Committed by web-flow

Commit Message

feat: extract shared tsoracle-failpoint crate (#306)

The failpoint! macro was duplicated byte-for-byte across four crates
(tsoracle-paxos-toolkit, tsoracle-openraft-toolkit, tsoracle-driver-file,
tsoracle-server) and had drifted in name (fail_point! in paxos vs
failpoint! elsewhere). Every change to failpoint semantics had to be made
N times.

Extract a tsoracle-failpoint micro-crate that owns the single failpoint!
macro and the only dependency on fail-rs in the workspace. The macro
expands through $crate::fail::fail_point!, and fail is re-exported
(failpoints-gated) so both the expansion and test registry calls route
through one crate -- consumers no longer name fail themselves.

- Delete the four per-crate failpoint.rs wrappers; consumers invoke
  tsoracle_failpoint::failpoint!(...) directly (matching the
  tsoracle-yieldpoint precedent) and forward
  failpoints = ["tsoracle-failpoint/failpoints"].
- Unify the macro name to failpoint! (paxos's lone fail_point! site updated).
- Route test registry access (cfg/FailScenario/cfg_callback/remove) through
  tsoracle_failpoint::fail in the in-crate and tsoracle-tests suites.
- Update docs/failpoint-testing.md and docs/yieldpoint-testing.md.

Lands as feat (not refactor) so the new crate publishes ahead of its
dependents. benchmarks/stress is untouched: it serializes a FAILPOINTS=
env string for child processes and never uses the macro or registry API.

Closes #263

Coverage Stats

21 of 21 new or added lines in 6 files covered. (100.0%)

1 existing line in 1 file now uncovered.

11267 of 11871 relevant lines covered (94.91%)

457738.93 hits per line