Skip to content

Replace absolute timing assertion with relative comparison#506

Merged
gcomte merged 1 commit intomasterfrom
fix/timing-dependent-test
Mar 30, 2026
Merged

Replace absolute timing assertion with relative comparison#506
gcomte merged 1 commit intomasterfrom
fix/timing-dependent-test

Conversation

@gcomte
Copy link
Copy Markdown
Owner

@gcomte gcomte commented Mar 30, 2026

Summary

  • The caching test asserted the first API call takes >1000μs, which is fragile on fast networks with warm DNS caches
  • Now asserts the cached second call is at least 10x faster than the first — tests the caching behavior, not network latency

The caching test asserted the first API call takes >1ms (absolute),
which is fragile on fast networks. Now asserts the cached call is
at least 10x faster than the first.
@gcomte gcomte merged commit ee035f2 into master Mar 30, 2026
6 checks passed
@gcomte gcomte deleted the fix/timing-dependent-test branch March 30, 2026 07:59
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