-
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
bench/rttanalysis: TestBenchmarkExpectation failed #74396
Comments
bench/rttanalysis.TestBenchmarkExpectation failed with artifacts on master @ 5aefc070d1e7f5bfd860eae24dea2e7726dc6d8c:
Help
See also: How To Investigate a Go Test Failure (internal)
Same failure on other branches
|
bench/rttanalysis.TestBenchmarkExpectation failed with artifacts on master @ bed5b793f9ed223b8133fad72f401ae8d02e8771:
Help
See also: How To Investigate a Go Test Failure (internal)
Same failure on other branches
|
bench/rttanalysis.TestBenchmarkExpectation failed with artifacts on master @ 72655fd4730fadb0ddacd8a5513a5d2d9121cbc6:
Help
See also: How To Investigate a Go Test Failure (internal)
Same failure on other branches
|
bench/rttanalysis.TestBenchmarkExpectation failed with artifacts on master @ 6aa6c727b1d990bc0e3e8fbc36e25fc358ba39c1:
Help
See also: How To Investigate a Go Test Failure (internal)
Same failure on other branches
|
Speculative analysis: recent failures coincide with #73876 landing. A possible culprit might be the same sort as #75304 (test not expecting stale distsender caches). Not assigning it to myself to investigate/fix (working through other fallout at the moment), but will get to it if this nobody gets to it before. |
bench/rttanalysis.TestBenchmarkExpectation failed with artifacts on master @ f8a330b7f750fb2c5faf4109c80d99ba9aac3070:
Help
See also: How To Investigate a Go Test Failure (internal)
Same failure on other branches
|
bench/rttanalysis.TestBenchmarkExpectation failed with artifacts on master @ 66d7d6884ff86eddb9a782a3670f7154ffa181c6:
Help
See also: How To Investigate a Go Test Failure (internal)
Same failure on other branches
|
Only had the most cursory look here. The failures do line up with when #73876 landed, but to the best of my knowledge, we didn't make anything faster. I'm not sure what to make of the variances above, what's contributing to it, and how #73876 fits in. There's more scanning of the system.descriptors now with the reconciliation job, so maybe distsender caches are pre-emptively primed? Or descriptors leased before the benchmarks expected them to be, reducing RTTs? (#75304 may be of interest to readers.) I'll just let this issue sit on SQL Schema's plate, though perhaps noting that it is indeed flakier than before and perhaps should be skipped and/or have the expectations file be more permissive wrt RTT ranges. |
We've had some flakes lately. One hypothesis I had was that we were seeing a restart. Indeed when I added an extra iteration, it shook out the numbers we were seeing. I didn't dig very deeply. I imagine there's something interesting there. However, I just want stable tests. Fixes cockroachdb#74396 Release note: None
bench/rttanalysis.TestBenchmarkExpectation failed with artifacts on master @ 659fe193978a65187fcce81e985e14f9e2de9606:
Help
See also: How To Investigate a Go Test Failure (internal)
Same failure on other branches
|
bench/rttanalysis.TestBenchmarkExpectation failed with artifacts on master @ d19fe5e61ae19b53cda5351449fb9172c2ccec63:
Help
See also: How To Investigate a Go Test Failure (internal)
Parameters in this failure:
Same failure on other branches
This test on roachdash | Improve this report!
The text was updated successfully, but these errors were encountered: