-
Notifications
You must be signed in to change notification settings - Fork 2.7k
[chore][processor/remotetap] Fix flaky tests #32970
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
Conversation
Test is now passing
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thank you for fixing!
Approved by approver and code owner, added |
Test failures are only for ARM and don't seem to relate to the functionality changed by this PR. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks @crobert-1
Description:
I added more information on the issue, but it seems like the limiter being used is especially flaky with timing in tests, so if too many metrics/traces/logs are being sent, the limit won't get fully hit as expected, meaning data will count as two separate intervals in the test (thus not being limited properly). This is flakiness in testing, not the rate limiter's fault, from what I can tell.
Also, in
assert.Equal
, the expected value should be first, and the actual value should be second. I've swapped these as the original output of the test failure was causing me confusion.Link to tracking Issue:
Resolves #32967