-
Notifications
You must be signed in to change notification settings - Fork 3.8k
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
kv/kvserver: TestTenantRateLimiter failed #70456
Comments
kv/kvserver.TestTenantRateLimiter failed with artifacts on master @ 85b1e92455eb2795043d71e5766b1b56dab308f2:
ReproduceTo reproduce, try: make stressrace TESTS=TestTenantRateLimiter PKG=./pkg/kv/kvserver TESTTIMEOUT=5m STRESSFLAGS='-timeout 5m' 2>&1 Parameters in this failure:
|
The failure is on this line:
It's curious that it doesn't output anything. There should be a message "X does not contain Y", and the objects we're passing to Think we'll need to repro this to see what's going on. |
Interesting, I was also looking into this and hadn't excluded getMetrics() from what I was looking at. It seems to happen in CI under bazel a bit more often than the non-bazel job. |
kv/kvserver.TestTenantRateLimiter failed with artifacts on master @ a0d6d46d3283be18483e3d449adc7d90a02649c1:
ReproduceTo reproduce, try: make stressrace TESTS=TestTenantRateLimiter PKG=./pkg/kv/kvserver TESTTIMEOUT=5m STRESSFLAGS='-timeout 5m' 2>&1 Parameters in this failure:
|
Refs: cockroachdb#70456 Reason: flaky test Generated by bin/skip-test. Release justification: non-production code changes Release note: None
68740: opt: support BYTES for histogram range calculations r=mgartner a=mgartner Fixes #68346 Release note (performance improvement): The accuracy of histogram calculations for BYTES types has been improved. As a result, the optimizer should generate more efficient query plans in some cases. 70710: kv/kvserver: skip TestTenantRateLimiter r=aayushshah15 a=tbg Refs: #70456 Reason: flaky test Generated by bin/skip-test. Release justification: non-production code changes Release note: None Co-authored-by: Marcus Gartner <[email protected]> Co-authored-by: Tobias Grieger <[email protected]>
I can repro locally. Instead of
we have
Some background write has snuck in and messed with out strict check. Almost surely triggered by my recent change to increase the limits. |
I'm not sure exactly how it happens, but I think it's because the metrics string is very long. |
70723: kv: deflake TestTenantRateLimiter r=RaduBerinde a=RaduBerinde A recent change (#70328) increased the rate limit and that exposed a fragility in this test. This change restores the test to use the original (small) rate limit. Fixes #70456. Release note: None Release justification: test-only fix. Co-authored-by: Radu Berinde <[email protected]>
kv/kvserver.TestTenantRateLimiter failed with artifacts on master @ bfdcfa00836232b910cb0fd109ebedf8913b1466:
Reproduce
To reproduce, try:
Parameters in this failure:
This test on roachdash | Improve this report!
The text was updated successfully, but these errors were encountered: