Skip to content

Fix flaky specs due to rate limiter change

What does this MR do and why?

This fixes flaky specs due to the change I made to the rate limiter: !73343 (merged)

We're now counting requests in the rate limiter based on fixed 1-minute buckets instead of 1-minute from the first request. So if the test is run near the end of the minute (e.g. ::59), the next requests would fall into the next bucket which means it won't go over the rate limit.

MR acceptance checklist

This checklist encourages us to confirm any changes have been analyzed to reduce risks in quality, performance, reliability, security, and maintainability.

Related to #345422 (closed)

Edited by Heinrich Lee Yu

Merge request reports