Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Backport 2.x] HeapBasedRateTracker uses time provider to allow simluating of time in unit tests #3941

Merged
merged 1 commit into from
Jan 11, 2024

Conversation

opensearch-trigger-bot[bot]
Copy link
Contributor

Backport 37d3ca2 from #3934.

…n unit tests (#3934)

Signed-off-by: Peter Nied <[email protected]>
(cherry picked from commit 37d3ca2)
Signed-off-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com>
Copy link

codecov bot commented Jan 11, 2024

Codecov Report

All modified and coverable lines are covered by tests ✅

Comparison is base (23985df) 65.07% compared to head (fcc2939) 65.21%.

Additional details and impacted files

Impacted file tree graph

@@            Coverage Diff             @@
##              2.x    #3941      +/-   ##
==========================================
+ Coverage   65.07%   65.21%   +0.13%     
==========================================
  Files         297      297              
  Lines       21024    21027       +3     
  Branches     3444     3444              
==========================================
+ Hits        13682    13712      +30     
+ Misses       5636     5607      -29     
- Partials     1706     1708       +2     
Files Coverage Δ
...curity/util/ratetracking/HeapBasedRateTracker.java 73.27% <100.00%> (+23.71%) ⬆️

... and 1 file with indirect coverage changes

@willyborankin willyborankin merged commit 1ff15c6 into 2.x Jan 11, 2024
88 checks passed
@willyborankin willyborankin deleted the backport/backport-3934-to-2.x branch January 11, 2024 19:00
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.

2 participants