Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
[chore][processor/remotetap] Fix flaky tests (#32970)
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. Resolves #32967
- Loading branch information