Fix test_throughput_consistency: replace np.datetime64 timing with time.perf_counter_ns#3
Merged
Conversation
Copilot
AI
changed the title
[WIP] Fix failing GitHub Actions job 'test'
Fix test_throughput_consistency: replace np.datetime64 timing with time.perf_counter_ns
Jun 5, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
test_throughput_consistencyalways failed in CI becausenp.datetime64('now')has only microsecond resolution — the timed operation completes in <1μs, so all latencies measured as0.0, producing0/0 = nanwhich fails the< 0.2assertion.Changes
np.datetime64('now')withtime.perf_counter_ns()(nanosecond integer, no floating-point rounding)min_latency < 100 nsrather than== 0— catches unrealistically small values even with a proper timer