Skip to content

Give the blocking driver the same coverage as the async one - #3

Merged
azeemshaik025 merged 1 commit into
mainfrom
jitter
Aug 9, 2026
Merged

Give the blocking driver the same coverage as the async one#3
azeemshaik025 merged 1 commit into
mainfrom
jitter

Conversation

@azeemshaik025

Copy link
Copy Markdown
Owner

No description provided.

Two gaps, both found by asking whether blocking was actually done.

The blocking driver had no test driving a randomized backoff at all. Both
drivers take any `Backoff`, and ADR001 decision 3 says they must not
diverge, but the coverage had: async proved jitter and decorrelated work
through the real driver and blocking proved neither.

And the `Clock for &C` / `Arc<C>` impls this release adds had no in-repo
test on either side. They were verified from an external crate while
writing them, which is not the same as being guarded. Deleting them now
fails the build with four E0599s instead of passing silently.

Both drivers now carry the same three tests: jittered, decorrelated, and a
borrowed-or-shared clock.
@azeemshaik025
azeemshaik025 merged commit 446b0a6 into main Aug 9, 2026
14 checks passed
@azeemshaik025
azeemshaik025 deleted the jitter branch August 9, 2026 11:45
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant