prisma-risk / tsoracle / 26371766671
95%

DEFAULT BRANCH: main
Ran
Jobs 1
Files 75
Run time 1min
Badge
Embed ▾
README BADGES
x

If you need to use a raster PNG badge, change the '.svg' to '.png' in the link

Markdown

Textile

RDoc

HTML

Rst
coverage: 94.895% (-0.02%) from 94.912%
26371766671

push

github

web-flow 
test(client): run the e2e + freshness client tests under turmoil DST (#309)

The high-level tsoracle_client::Client can already be driven over turmoil: the
public ClientBuilder::channel_connector hook lets a caller own channel
construction per endpoint (configured endpoints and leader-hint redirects
alike), and tonic's lazy Channel keeps the !Send turmoil IO on the sim's
connection task behind a Send handle — so the client's coalescing driver
(which tokio::spawns) compiles and runs unchanged. No change to the published
client crate was needed.

Add test_support::dst::sim_channel(endpoint) — the per-endpoint building block
that dials over the turmoil network — and convert the client tests to build
their Client via channel_connector delegating to it:

- client_e2e_dst.rs: get-ts-against-leader, two-host leader-hint redirect,
  hintless-follower error surfacing, and 32-way concurrent coalescing (join_all
  instead of OS-thread spawn). A fixed near-epoch Clock clears the >1.7e12
  assertions.
- client_freshness_dst.rs: the freshness contract (physical_ms >= enqueue time)
  against a SharedClock the test also reads — exact (no wall-clock tolerance)
  and deterministic, vs the original's 2ms SystemTime race.

Replaces the real-time originals (client_e2e.rs, client_freshness.rs). All run
deterministically and instantly under turmoil.

11265 of 11871 relevant lines covered (94.9%)

462620.58 hits per line

Coverage Regressions

Lines Coverage ∆ File
2
84.37
 -0.54% benchmarks/stress/src/topology/paxos.rs
Jobs
ID Job ID Ran Files Coverage
1 26371766671.1 75
94.9
 GitHub Action Run
Source Files on build 26371766671